Integer overflow in imlib2 before 1.4.9 on 32-bit platforms allows remote attackers to execute arbitrary code via large dimensions in an image, which triggers an out-of-bounds heap memory write operation.
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
Link | Tags |
---|---|
https://git.enlightenment.org/legacy/imlib2.git/commit/?id=7eba2e4c8ac0e20838947f10f29d0efe1add8227 | vendor advisory |
https://sourceforge.net/p/enlightenment/mailman/message/35055012/ | mailing list patch vendor advisory |
https://security.gentoo.org/glsa/201611-12 | third party advisory vendor advisory |
http://www.debian.org/security/2016/dsa-3555 | third party advisory vendor advisory |
http://www.securitytracker.com/id/1035573 | vdb entry third party advisory |
http://www.securityfocus.com/bid/86073 | vdb entry third party advisory |
http://lists.opensuse.org/opensuse-updates/2016-05/msg00076.html | third party advisory vendor advisory |