Application crash via overflowing framebuffer dimensions
Published Dec 11, 2023 · Updated Aug 2, 2024
Buffer overflow in afichet OpenEXR Viewer before 0.6.1 allows context-dependent attackers to crash the application via a crafted EXR file. RGBFramebufferModel and YFramebufferModel multiply untrusted 32-bit image dimensions when sizing frame buffers without first checking for integer overflow. The file must be opened in the desktop viewer; the published proof demonstrates an out-of-bounds write and access-violation crash, while code execution is not established.
Summary
What happened
Buffer overflow in afichet OpenEXR Viewer before 0.6.1 allows context-dependent attackers to crash the application via a crafted EXR file. RGBFramebufferModel and YFramebufferModel multiply untrusted 32-bit image dimensions when sizing frame buffers without first checking for integer overflow. The file must be opened in the desktop viewer; the published proof demonstrates an out-of-bounds write and access-violation crash, while code execution is not established.
The record
- CVE
- CVE-2023-50245
- Published
- Dec 11, 2023
- Updated
- Aug 2, 2024
- Vendor
- afichet
- Product
- OpenEXR Viewer
- Classifications
- CWE-120, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 11, 2023CVE publishedPublication date reported by the CVE source.
- Aug 2, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 0.6.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo