Code execution via invalid JPEG decoder write
Published Feb 6, 2020 · Updated Aug 6, 2024
A write access violation in JPEGsnoop 1.5.2 allows context-dependent attackers to execute arbitrary code through a crafted JPEG file. During JPEG decoding, the instruction at JPEGsnoop executable offset 0xc8ae writes a 16-bit value through an invalid computed address, causing memory corruption. The published Windows proof of concept demonstrates an application crash; the CVE record asserts arbitrary code execution but provides no demonstrated execution payload.
Summary
What happened
A write access violation in JPEGsnoop 1.5.2 allows context-dependent attackers to execute arbitrary code through a crafted JPEG file. During JPEG decoding, the instruction at JPEGsnoop executable offset 0xc8ae writes a 16-bit value through an invalid computed address, causing memory corruption. The published Windows proof of concept demonstrates an application crash; the CVE record asserts arbitrary code execution but provides no demonstrated execution payload.
The record
- CVE
- CVE-2012-6307
- Published
- Feb 6, 2020
- Updated
- Aug 6, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 6, 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?
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
- JPEGsnoop 1.5.2 - WriteAV Crash (PoC)proof of concept · demonstrated
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