ChromeWeb browser · Google
CVE-2016-1651
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedfxcodec/codec/fx_codec_jpx_opj.cpp in PDFium, as used in Google Chrome before 50.0.2661.75, does not properly implement the sycc420_to_rgb and sycc422_to_rgb functions, which allows remote attackers to obtain sensitive information from process memory or cause a denial of service (out-of-bounds read) via crafted JPEG 2000 data in a PDF document.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOut-of-bounds read vulnerability in PDFium's JPEG 2000 codec (fx_codec_jpx_opj.cpp). The sycc420_to_rgb and sycc422_to_rgb color conversion functions lack proper bounds checking when processing crafted JPEG 2000 data embedded in PDF documents, allowing attackers to read sensitive process memory or cause crashes.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
ChromeWeb browser
<= 49.0.2623.112
Debian LinuxOperating system
= 8.0= 42.1= 12.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminal to see the installed Chrome versionAffected if Installed version is 49.0.2623.112 or earlier
-
Identify if PDFium library is in useSearch for libpdfium.so or pdfium.dll in the system, or check if any application explicitly links against PDFiumAffected if PDFium library is present and its version cannot be verified as patched or is from an unpatched build
-
Determine if PDF processing with JPEG 2000 support is enabledCheck if any installed software can process PDF documents containing JPEG 2000 images - this is a built-in capability in PDF-capable applicationsAffected if The system runs software that parses PDF files with embedded JPEG 2000 imagery
-
Verify operating system version for Debian 8.0Run 'cat /etc/debian_version' or 'lsb_release -a' to confirm the Debian installationAffected if System runs Debian 8.0 with unpatched Chrome or PDFium packages
-
Verify operating system version for SUSE-based systemsRun 'cat /etc/os-release' or 'hostnamectl' to check if running OpenSUSE Leap 42.1 or SUSE Linux Enterprise 12.0Affected if System runs OpenSUSE Leap 42.1 or SUSE Linux Enterprise 12.0 with vulnerable Chrome or PDFium packages
A user is affected if they run Google Chrome version 49.0.2623.112 or earlier, or any PDFium-based application on Debian 8.0, OpenSUSE Leap 42.1, or SUSE Linux Enterprise 12.0 that processes PDF documents with JPEG 2000 images.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate Google Chrome to version 50.0.2661.75 or later. For applications using PDFium directly, update to the patched PDFium version that fixes the bounds checking in the sycc420_to_rgb and sycc422_to_rgb functions.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-1651 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data