Application crash via invalid EXR memory write
Published Aug 28, 2024 · Updated Aug 28, 2024
Memory corruption in IrfanView 4.67.1.0 allows attackers to crash the application by opening a crafted EXR image. Exr.dll's ReadEXR routine performs a 128-bit write through an invalid destination address while decoding attacker-controlled EXR data. Exploitation requires a user to open the file, and the demonstrated consequence is termination of the IrfanView process.
Summary
What happened
Memory corruption in IrfanView 4.67.1.0 allows attackers to crash the application by opening a crafted EXR image. Exr.dll's ReadEXR routine performs a 128-bit write through an invalid destination address while decoding attacker-controlled EXR data. Exploitation requires a user to open the file, and the demonstrated consequence is termination of the IrfanView process.
The record
- CVE
- CVE-2024-44915
- Published
- Aug 28, 2024
- Updated
- Aug 28, 2024
- Vendor
- IrfanView Software
- Product
- IrfanView
- Classifications
- CWE-284, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 28, 2024CVE publishedPublication date reported by the CVE source.
- Aug 28, 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=4.67.1.0
What conditions does exploitation require?
What is affected?
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.
Public exploit references
- IrfanView crafted EXR proof of conceptproof of concept · demonstrated
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