CVE-2025-64182
BaseFortify
Publication date: 2025-11-10
Last updated on: 2025-12-08
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openexr | openexr | From 3.2.0 (inc) to 3.2.5 (exc) |
| openexr | openexr | From 3.3.0 (inc) to 3.3.6 (exc) |
| openexr | openexr | From 3.4.0 (inc) to 3.4.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-120 | The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a memory safety bug in the legacy OpenEXR Python adapter (the deprecated OpenEXR.InputFile wrapper) present in certain versions of OpenEXR. It involves integer overflow and unchecked memory allocation in the InputFile.channel() and InputFile.channels() functions, which can lead to heap overflow on 32-bit systems or a NULL pointer dereference on 64-bit systems. This can cause crashes and potentially allow code execution when opening specially crafted EXR files or passing crafted Python objects.
How can this vulnerability impact me? :
The vulnerability can cause application crashes and potentially allow an attacker to execute arbitrary code when processing malicious EXR files or crafted Python objects using the affected OpenEXR Python adapter versions. This could lead to denial of service or compromise of the system running the vulnerable software.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, update OpenEXR to versions 3.2.5, 3.3.6, or 3.4.3 or later, which contain patches for the issue. Avoid opening untrusted or attacker-controlled EXR files using the legacy OpenEXR Python adapter until the update is applied.