Write access violation via crafted XPM file
Published Dec 15, 2021 · Updated Aug 4, 2024
Memory corruption in IrfanView 4.54 allows context-dependent attackers to trigger a user-mode write access violation through an XPM file. FORMATS.dll's ReadXPM_W path writes a byte to an invalid address derived while parsing crafted XPM data. Exploitation is local and requires a user to open the crafted image; public evidence demonstrates the invalid write but not code execution.
Summary
What happened
Memory corruption in IrfanView 4.54 allows context-dependent attackers to trigger a user-mode write access violation through an XPM file. FORMATS.dll's ReadXPM_W path writes a byte to an invalid address derived while parsing crafted XPM data. Exploitation is local and requires a user to open the crafted image; public evidence demonstrates the invalid write but not code execution.
The record
- CVE
- CVE-2020-23545
- Published
- Dec 15, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 15, 2021CVE publishedPublication date reported by the CVE source.
- Aug 4, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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