Code execution via malformed RLE strip length
Published Jan 2, 2020 · Updated Aug 6, 2024
Heap-based buffer overflow in XnView Classic before 2.13 allows remote attackers to execute arbitrary code via a crafted RGB file. xnview.exe sign-extends the untrusted RLE strip size and then copies strip data without adequate bounds checking, overflowing a heap buffer. Exploitation requires a user to open the file; successful execution runs with the privileges of the XnView process.
Summary
What happened
Heap-based buffer overflow in XnView Classic before 2.13 allows remote attackers to execute arbitrary code via a crafted RGB file. xnview.exe sign-extends the untrusted RLE strip size and then copies strip data without adequate bounds checking, overflowing a heap buffer. Exploitation requires a user to open the file; successful execution runs with the privileges of the XnView process.
The record
- CVE
- CVE-2013-3939
- Published
- Jan 2, 2020
- Updated
- Aug 6, 2024
- Vendor
- XnSoft
- Product
- XnView Classic
- Classifications
- CWE-787, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jan 2, 2020CVE publishedPublication date reported by the CVE source.
- Aug 6, 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=before 2.13
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.
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