Process memory corruption via B3D heap overwrite
Published Jan 5, 2024 · Updated Jun 17, 2025
Heap-based out-of-bounds write in IrfanView B3D PlugIns before 4.56 allows attackers to corrupt process memory via a crafted B3D file. B3d.dll writes past a heap allocation at module offset +27ef while loading B3D content; public reports omit the malformed field and faulty size calculation. The vulnerable plug-in must process attacker-controlled B3D content, and the proven consequence is process-memory corruption without a published post-corruption outcome.
Summary
What happened
Heap-based out-of-bounds write in IrfanView B3D PlugIns before 4.56 allows attackers to corrupt process memory via a crafted B3D file. B3d.dll writes past a heap allocation at module offset +27ef while loading B3D content; public reports omit the malformed field and faulty size calculation. The vulnerable plug-in must process attacker-controlled B3D content, and the proven consequence is process-memory corruption without a published post-corruption outcome.
The record
- CVE
- CVE-2020-13878
- Published
- Jan 5, 2024
- Updated
- Jun 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-787, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 5, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record 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.
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