CVE-2016-1628: pi.c in OpenJPEG, as used in PDFium in Google Chrome before 48.0.2564.109, does not validate a certain precision value, which allows remote…
Noroxi assessment
Priority: Monitor (action score 26/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 1.8% (FIRST EPSS); higher than 79.8% of all records.
- Anyone who can reach it over the internet can trigger it. No account or password is required. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: openjpeg2 (Debian:12) 2.1.2-1.2; chromium-browser (Debian:8) 48.0.2564.116-1~deb8u1; openjpeg2 (Debian:8) 2.1.0-2+deb8u3.
Low priority for now. Upgrade to openjpeg2 (Debian:12) 2.1.2-1.2; chromium-browser (Debian:8) 48.0.2564.116-1~deb8u1; openjpeg2 (Debian:8) 2.1.0-2+deb8u3 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
pi.c in OpenJPEG, as used in PDFium in Google Chrome before 48.0.2564.109, does not validate a certain precision value, which allows remote attackers to execute arbitrary code or cause a denial of service (out-of-bounds read) via a crafted JPEG 2000 image in a PDF document, related to the opj_pi_next_rpcl, opj_pi_next_pcrl, and opj_pi_next_cprl functions.
- Published
- Feb 21, 2016
- Updated
- Jun 16, 2026
- EPSS
- 1.8% · 79th percentile
- CWE
- CWE-119
Report tools
Action score
26
Low priority for now.
- CVSS
- 25 / 40 · 6.3 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 1 / 30 · 1.8%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- debian debian linux8.0
- google chromeup to 48.0.2564.103 inclusive
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | openjpeg2 | before 2.1.2-1.2 | 2.1.2-1.2 |
| Debian:8 | chromium-browser | before 48.0.2564.116-1~deb8u1 | 48.0.2564.116-1~deb8u1 |
| Debian:8 | openjpeg2 | before 2.1.0-2+deb8u3 | 2.1.0-2+deb8u3 |
| Debian:9 | openjpeg2 | before 2.1.2-1.1+deb9u2 | 2.1.2-1.1+deb9u2 |
| Red Hat:rhel_extras:6 | chromium-browser | before 0:48.0.2564.109-1.el6 | 0:48.0.2564.109-1.el6 |
| Red Hat:rhel_extras:6 | chromium-browser-debuginfo | before 0:48.0.2564.109-1.el6 | 0:48.0.2564.109-1.el6 |
Same product
google: all recordsOther highest-scoring records for the same primary product.
- CVE-2023-4863Heap buffer overflow in libwebp in Google Chrome prior to 116.0.5845.187 and libwebp 1.3.2 allowed a remote attacker to perform an out of…KEV95Now
- CVE-2021-21224Type confusion in V8 in Google Chrome prior to 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox via a…KEV90Now
- CVE-2018-17463Incorrect side effect annotation in V8 in Google Chrome prior to 70.0.3538.64 allowed a remote attacker to execute arbitrary code inside a…KEV90Now
Published before and after this one in the same product
- ← EarlierCVE-2016-1626Feb 13, 2016 · The opj_pi_update_decode_poc function in pi.c in OpenJPEG, as used in PDFium in Google Chrome before 48.0.2564.109, miscalculates a certain…17Monitor
- ← EarlierCVE-2016-1627Feb 13, 2016 · The Developer Tools (aka DevTools) subsystem in Google Chrome before 48.0.2564.109 does not validate URL schemes and ensure that the…35Monitor
- Later →CVE-2016-1629Feb 21, 2016 · Google Chrome before 48.0.2564.116 allows remote attackers to bypass the Blink Same Origin Policy and a sandbox protection mechanism via…40Plan
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:chromium-browser | 48.0.2564.116-1~deb8u1 · Debian:8 | Package registry (OSV) |
| debian:openjpeg2 | 2.1.2-1.2 · Debian:12 | Package registry (OSV) |
| red hat:chromium-browser | 0:48.0.2564.109-1.el6 · Red Hat:rhel_extras:6 | Package registry (OSV) |
| red hat:chromium-browser-debuginfo | 0:48.0.2564.109-1.el6 · Red Hat:rhel_extras:6 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- No account or password is required.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- low · data can be read
- Integrity
- low · data or configuration can be modified
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- Low
- Integrity impact
- Low
- Availability impact
- Low
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (10 more)Show less
- rhn.redhat.com/errata/RHSA-2016-0241.html
- www.debian.org/security/2016/dsa-3486
- www.debian.org/security/2017/dsa-4013
- www.securityfocus.com/bid/83125
- www.securitytracker.com/id/1035183
- www.zerodayinitiative.com/advisories/ZDI-16-172/
- code.google.com/p/chromium/issues/detail?id=571479
- codereview.chromium.org/1590593002
- security.gentoo.org/glsa/201603-09
- security.gentoo.org/glsa/201710-26
Vendor advisories and official records. Exploit/PoC links are deliberately left out.