OpenEXR provides the specification and reference implementation of the EXR file format, an image storage format for the motion picture industry. From 3.1.0 to before 3.2.7, 3.3.9, and 3.4.9, internal_exr_undo_piz() advances the working wavelet pointer with signed 32-bit arithmetic. Because nx, ny, and wcount are int, a crafted EXR file can make this product overflow and wrap. The next channel then decodes from an incorrect address. The wavelet decode path operates in place, so this yields both out-of-bounds reads and out-of-bounds writes. This vulnerability is fixed in 3.2.7, 3.3.9, and 3.4.9.
Weakness
The product reads data past the end, or before the beginning, of the intended buffer.
Affected Software
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Openexr | Openexr | 3.1.0 (including) | 3.2.7 (excluding) |
| Openexr | Openexr | 3.3.0 (including) | 3.3.9 (excluding) |
| Openexr | Openexr | 3.4.0 (including) | 3.4.9 (excluding) |
| Red Hat Enterprise Linux 10 | RedHat | openexr-0:3.1.10-8.el10_1.2 | * |
| Red Hat Enterprise Linux 10 | RedHat | openexr-0:3.1.10-8.el10_2.2 | * |
| Red Hat Enterprise Linux 10.0 Extended Update Support | RedHat | openexr-0:3.1.10-8.el10_0.2 | * |
| Red Hat Enterprise Linux 9 | RedHat | openexr-0:3.1.1-3.el9_7.2 | * |
| Red Hat Enterprise Linux 9 | RedHat | openexr-0:3.1.1-3.el9_8.2 | * |
| Red Hat Enterprise Linux 9.0 Update Services for SAP Solutions | RedHat | openexr-0:3.1.1-2.el9_0.3 | * |
| Red Hat Enterprise Linux 9.2 Update Services for SAP Solutions | RedHat | openexr-0:3.1.1-2.el9_2.3 | * |
| Red Hat Enterprise Linux 9.4 Extended Update Support | RedHat | openexr-0:3.1.1-2.el9_4.3 | * |
| Red Hat Enterprise Linux 9.6 Extended Update Support | RedHat | openexr-0:3.1.1-3.el9_6.2 | * |
| Red Hat AI Inference Server 3.3 | RedHat | rhaiis/model-opt-cuda-rhel9:1782352950 | * |
| Openexr | Ubuntu | devel | * |
| Openexr | Ubuntu | esm-apps/noble | * |
| Openexr | Ubuntu | esm-apps/resolute | * |
| Openexr | Ubuntu | noble | * |
| Openexr | Ubuntu | questing | * |
| Openexr | Ubuntu | resolute | * |
| Openexr | Ubuntu | upstream | * |
Potential Mitigations
- Assume all input is malicious. Use an “accept known good” input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
- When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, “boat” may be syntactically valid because it only contains alphanumeric characters, but it is not valid if the input is only expected to contain colors such as “red” or “blue.”
- Do not rely exclusively on looking for malicious or malformed inputs. This is likely to miss at least one undesirable input, especially if the code’s environment changes. This can give attackers enough room to bypass the intended validation. However, denylists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.
- To reduce the likelihood of introducing an out-of-bounds read, ensure that you validate and ensure correct calculations for any length argument, buffer size calculation, or offset. Be especially careful of relying on a sentinel (i.e. special character such as NUL) in untrusted inputs.
Related Attack Patterns
References
- https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.2.7
- https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.3.9
- https://github.com/AcademySoftwareFoundation/openexr/releases/tag/v3.4.9
- https://github.com/AcademySoftwareFoundation/openexr/security/advisories/GHSA-588r-cr5c-w6hf