Heap-based Buffer Overflow in OpenJPEG opj_mqc_byteout
A heap-based buffer overflow exists in the opj_mqc_byteout function in mqc.c in OpenJPEG versions prior to 2.2.0. This vulnerability can be triggered by a specially crafted BMP file, which causes the application to write outside the bounds of a heap-allocated buffer, leading to memory corruption and a potential application crash.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Exploitation of this vulnerability allows remote attackers to cause a denial of service (application crash) by sending a crafted BMP file to an application using a vulnerable version of OpenJPEG. While the primary impact is denial of service, memory corruption could potentially be leveraged for further exploitation, though no such exploitation has been demonstrated.
If you can’t patch tonight, do this now.
If immediate upgrade is not possible, restrict processing of untrusted BMP files and consider running applications using OpenJPEG in a sandboxed environment to limit the impact of potential exploitation.
Patch, then assume compromise.
Upgrade OpenJPEG to version 2.2.0 or later, where the vulnerable code in opj_mqc_byteout has been patched to prevent the buffer overflow condition.
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.