CVE-2016-8332
CVE-2016-8332 Vulnerability Analysis & Exploit Intelligence
A buffer overflow in OpenJPEG 2.1.1 causes arbitrary code execution when parsing a crafted image. An exploitable code execution vulnerability exists in the jpeg2000 image file format parser as implemented in the OpenJpeg library. A specially crafted jpeg2000 file can cause an out of bound heap write resulting in heap corruption leading to arbitrary code execution. For a successful attack, the target user needs to open a malicious jpeg2000 file. The jpeg2000 image file format is mostly used for embedding images inside PDF documents and the OpenJpeg library is used by a number of popular PDF renderers making PDF documents a likely attack vector.
Published Updated Sources: cvelistV5, talos
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
3%
chance of exploitation in 30 days
CVSS base
7.5
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.5 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
References
6 on the record
- www.debian.org/security/2017/dsa-3768
vendor-advisory, x_refsource_DEBIAN
- www.securityfocus.com/bid/93242
vdb-entry, x_refsource_BID
- www.securitytracker.com/id/1038623
vdb-entry, x_refsource_SECTRACK
- www.oracle.com/security-alerts/cpujul2020.html
x_refsource_MISC
- www.talosintelligence.com/reports/TALOS-2016-0193/
x_refsource_MISC
- github.com/uclouvain/openjpeg/releases/tag/v2.1.2
x_refsource_MISC
Elsewhere on this site
- openjpegevery CVE for this vendor
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.