A vulnerability exists in JPEGsnoop 1.5.2 due to an unspecified issue in JPEG file handling, which could let a malicious user execute arbitrary code
Loading...
Loading...
This high-severity CVE scores 8.8 under NVD CVSS v3. EPSS exploit probability: 4.1%, top 11% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
A vulnerability exists in JPEGsnoop 1.5.2 due to an unspecified issue in JPEG file handling, which could let a malicious user execute arbitrary code
February 6, 2020
November 21, 2024
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
JPEGsnoop 1.5.2 - WriteAV Crash (PoC)
Open source ↗See which npm, PyPI, Go, and Maven packages are affected by CVE-2012-6307
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.