A flaw was found in the OpenJPEG project. A heap buffer overflow condition may be triggered when certain options are specified while using the opj_decompress utility. This can lead to an application crash or other undefined behavior.
Weakness
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Red Hat Enterprise Linux 9 | RedHat | openjpeg2-0:2.4.0-8.el9 | * |
| Blender | Ubuntu | esm-apps/xenial | * |
| Blender | Ubuntu | focal | * |
| Blender | Ubuntu | oracular | * |
| Blender | Ubuntu | plucky | * |
| Ghostscript | Ubuntu | esm-infra-legacy/xenial | * |
| Ghostscript | Ubuntu | esm-infra/bionic | * |
| Ghostscript | Ubuntu | esm-infra/xenial | * |
| Insighttoolkit4 | Ubuntu | esm-apps/xenial | * |
| Insighttoolkit4 | Ubuntu | focal | * |
| Openjpeg2 | Ubuntu | devel | * |
| Openjpeg2 | Ubuntu | esm-apps-legacy/xenial | * |
| Openjpeg2 | Ubuntu | esm-apps/bionic | * |
| Openjpeg2 | Ubuntu | esm-apps/xenial | * |
| Openjpeg2 | Ubuntu | esm-infra/focal | * |
| Openjpeg2 | Ubuntu | focal | * |
| Openjpeg2 | Ubuntu | jammy | * |
| Openjpeg2 | Ubuntu | noble | * |
| Openjpeg2 | Ubuntu | oracular | * |
| Openjpeg2 | Ubuntu | plucky | * |
| Openjpeg2 | Ubuntu | questing | * |
| Openjpeg2 | Ubuntu | resolute | * |
| Openjpeg2 | Ubuntu | upstream | * |
| Qtwebengine-opensource-src | Ubuntu | focal | * |
| Qtwebengine-opensource-src | Ubuntu | oracular | * |
| Qtwebengine-opensource-src | Ubuntu | plucky | * |
| Texmaker | Ubuntu | esm-apps/xenial | * |
| Texmaker | Ubuntu | focal | * |
| Texmaker | Ubuntu | oracular | * |
| Texmaker | Ubuntu | plucky | * |
Potential Mitigations
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking.
- D3-SFCV (Stack Frame Canary Validation) from D3FEND [REF-1334] discusses canary-based detection in detail.
- Run or compile the software using features or extensions that randomly arrange the positions of a program’s executable and libraries in memory. Because this makes the addresses unpredictable, it can prevent an attacker from reliably jumping to exploitable code.
- Examples include Address Space Layout Randomization (ASLR) [REF-58] [REF-60] and Position-Independent Executables (PIE) [REF-64]. Imported modules may be similarly realigned if their default memory addresses conflict with other modules, in a process known as “rebasing” (for Windows) and “prelinking” (for Linux) [REF-1332] using randomly generated addresses. ASLR for libraries cannot be used in conjunction with prelink since it would require relocating the libraries at run-time, defeating the whole purpose of prelinking.
- For more information on these techniques see D3-SAOR (Segment Address Offset Randomization) from D3FEND [REF-1335].
Related Attack Patterns
References
- https://access.redhat.com/errata/RHSA-2025:7309
- https://access.redhat.com/security/cve/CVE-2024-56827
- https://bugzilla.redhat.com/show_bug.cgi?id=2335174
- https://github.com/uclouvain/openjpeg/commit/e492644fbded4c820ca55b5e50e598d346e850e8
- https://github.com/uclouvain/openjpeg/issues/1564
- https://lists.debian.org/debian-lts-announce/2025/04/msg00002.html