Use-after-free vulnerability in the opj_j2k_write_mco function in j2k.c in OpenJPEG before 2.1.1 allows remote attackers to have unspecified impact via unknown vectors.
The product reuses or references memory after it has been freed. At some point afterward, the memory may be allocated again and saved in another pointer, while the original pointer references a location somewhere within the new allocation. Any operations using the original pointer are no longer valid because the memory "belongs" to the code that operates on the new pointer.
Link | Tags |
---|---|
https://security.gentoo.org/glsa/201612-26 | vendor advisory |
https://github.com/uclouvain/openjpeg/issues/563 | issue tracking patch |
http://www.openwall.com/lists/oss-security/2016/05/13/1 | third party advisory mailing list |
https://github.com/uclouvain/openjpeg/blob/master/CHANGELOG.md | third party advisory release notes |
https://bugzilla.redhat.com/show_bug.cgi?id=1263359 | issue tracking |
http://www.debian.org/security/2016/dsa-3665 | third party advisory vendor advisory |
https://github.com/uclouvain/openjpeg/commit/940100c28ae28931722290794889cf84a92c5f6f | issue tracking patch |
http://www.securitytracker.com/id/1038623 | vdb entry |
http://www.openwall.com/lists/oss-security/2015/09/15/4 | third party advisory mailing list |