Code execution via malformed DXF file parsing
Published Nov 22, 2024 · Updated Nov 22, 2024
Memory corruption in IrfanView 4.67 allows context-dependent attackers to execute code by inducing a user to open a crafted DXF file. The DXF parser fails to validate user-supplied file data before memory operations, producing a corruption condition in the current process. Exploitation requires the target to visit a malicious page or open the file, and successful code runs with the current process privileges.
Summary
What happened
Memory corruption in IrfanView 4.67 allows context-dependent attackers to execute code by inducing a user to open a crafted DXF file. The DXF parser fails to validate user-supplied file data before memory operations, producing a corruption condition in the current process. Exploitation requires the target to visit a malicious page or open the file, and successful code runs with the current process privileges.
The record
- CVE
- CVE-2024-11538
- Published
- Nov 22, 2024
- Updated
- Nov 22, 2024
- Vendor
- IrfanView Software
- Product
- IrfanView
- Classifications
- CWE-787, CWE-119, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 22, 2024CVE publishedPublication date reported by the CVE source.
- Nov 22, 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.0.0
- Affected versionversion=4.67 <4.70
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