ChromeWeb browser · Google
CVE-2016-1619
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 · uneditedMultiple integer overflows in the (1) sycc422_to_rgb and (2) sycc444_to_rgb functions in fxcodec/codec/fx_codec_jpx_opj.cpp in PDFium, as used in Google Chrome before 48.0.2564.82, allow remote attackers to cause a denial of service (out-of-bounds read) or possibly have unspecified other impact via a crafted 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 confidenceInteger overflows in sycc422_to_rgb and sycc444_to_rgb functions in PDFium's JPEG 2000 codec (fx_codec_jpx_opj.cpp) allow out-of-bounds memory reads when processing crafted PDF documents with specially crafted image dimensions, potentially leading to denial of service or arbitrary code execution.
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
<= 47.0.2526.106CVSS 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
- Low
- Integrity
- Low
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/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 use 'Help > About Google Chrome' to view the installed version numberAffected if Version is 47.0.2526.106 or lower (the fixed version is 48.0.2564.82)
-
Identify PDFium version in embedded implementationsLocate the fx_codec_jpx_opj.cpp file in the codebase and check the source control history or version metadata for the sycc422_to_rgb and sycc444_to_rgb functionsAffected if The integer overflow checks (specifically bounds validation on width and height variables before array indexing) are absent from these functions
-
Verify if JPEG 2000 rendering is enabledCheck the PDF renderer configuration or build flags for PDFium; look for OPJ_ENABLED or similar flags that enable JPEG 2000 codec supportAffected if JPEG 2000 image decoding is enabled and the PDFium library is an unpatched version from before the fix
-
Inspect processed PDF documents for JPEG 2000 imagesUse a PDF parsing tool (such as pdfinfo or pdfid) to examine PDF files opened in Chrome or the embedded viewer, specifically looking for JPX (JPEG 2000) image streamsAffected if A specially crafted PDF containing JPEG 2000 images with malicious dimension values is being rendered
A user is affected if they are running Google Chrome version 47.0.2526.106 or lower, or any embedded PDFium implementation that lacks integer overflow protection in sycc422_to_rgb and sycc444_to_rgb functions when processing JPEG 2000 images with crafted dimensions.
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 48.0.2564.82 or later; for embedded PDFium implementations, patch the affected functions with proper integer overflow checks before array indexing operations.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1619 — 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-1619 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