dbcve.org
ChromeWeb browser · Google

CVE-2016-5139

HIGH · 7.6 CVSS v3.0 Published 2016-08-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
83/100
Remediation priority · High
Remotely reachable No privileges

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 · unedited
Multiple integer overflows in the opj_tcd_init_tile function in tcd.c in OpenJPEG, as used in PDFium in Google Chrome before 52.0.2743.116, allow remote attackers to cause a denial of service (heap-based buffer overflow) or possibly have unspecified other impact via crafted JPEG 2000 data.

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 confidence

Integer overflows in OpenJPEG's opj_tcd_init_tile function in tcd.c allow heap-based buffer overflows when processing crafted JPEG 2000 data. The vulnerability is exposed through PDFium in Google Chrome when rendering malicious PDF files containing specially crafted JPEG 2000 images.

MitigationUpdate Google Chrome to version 52.0.2743.116 or later. For applications using OpenJPEG directly, apply the vendor patch to fix the integer overflows in opj_tcd_init_tile or update to a patched OpenJPEG version.

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
Affected:= 52.0.2743.82

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version
    Navigate to chrome://settings/help or use 'About Google Chrome' in the Chrome menu to view the installed version
    Affected if The displayed version is exactly 52.0.2743.82
  2. Identify PDF processing context
    Determine if Google Chrome is used to render PDF files, as the vulnerability is triggered through PDFium when Chrome opens PDF documents
    Affected if Chrome is used as a PDF viewer and processes PDF files containing JPEG 2000 images
  3. Confirm JPEG 2000 usage in PDFs
    Inspect PDF files for embedded JPEG 2000 image streams (look for JPX, JP2, or JPEG 2000 compression methods in PDF metadata)
    Affected if PDF files processed by Chrome contain JPEG 2000 compressed images

You are affected if you are running Google Chrome version 52.0.2743.82 and open PDF files containing specially crafted JPEG 2000 images.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Google Chrome to version 52.0.2743.116 or later. For applications using OpenJPEG directly, apply the vendor patch to fix the integer overflows in opj_tcd_init_tile or update to a patched OpenJPEG version.

Fix this in Chrome Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5139 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-5139 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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