Memory corruption via invalid HDR byte write
Published Jun 10, 2020 · Updated Aug 4, 2024
Memory corruption in IrfanView 32-bit 4.54 allows context-dependent attackers to trigger an invalid write by supplying a crafted HDR file. The FORMATS.dll GetPlugInInfo routine writes a byte through an invalid destination pointer while parsing the untrusted HDR file. Exploitation requires a user to open the file with the 32-bit FORMATS plug-in, and published research establishes a user-mode access violation rather than code execution.
Summary
What happened
Memory corruption in IrfanView 32-bit 4.54 allows context-dependent attackers to trigger an invalid write by supplying a crafted HDR file. The FORMATS.dll GetPlugInInfo routine writes a byte through an invalid destination pointer while parsing the untrusted HDR file. Exploitation requires a user to open the file with the 32-bit FORMATS plug-in, and published research establishes a user-mode access violation rather than code execution.
The record
- CVE
- CVE-2020-13905
- Published
- Jun 10, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2020CVE 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