ChromeWeb browser · Google
CVE-2016-5158
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 opj_tcd_init_tile function in tcd.c in OpenJPEG, as used in PDFium in Google Chrome before 53.0.2785.89 on Windows and OS X and before 53.0.2785.92 on Linux, 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 confidenceInteger overflow vulnerability in OpenJPEG's opj_tcd_init_tile function (tcd.c) allows heap-based buffer overflow when processing specially crafted JPEG 2000 data. The flaw exists in PDFium (used by Google Chrome) and can be exploited remotely via malicious PDF files containing crafted JPEG 2000 images.
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
<= 52.0.2743.116= 42.1CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 identify the installed Chrome versionAffected if Version is 52.0.2743.116 or lower (the affected range ends at 52.0.2743.116)
-
Check OpenJPEG library version on OpenSUSE Leap 42.1Run 'rpm -qa | grep openjpeg' or 'zypper se openjpeg' to list installed OpenJPEG packages, then check the specific version with 'rpm -q --qf '%{VERSION}-%{RELEASE}' <package name>'Affected if OpenJPEG library version is present on OpenSUSE Leap 42.1 (the affected product/version combination listed)
-
Verify JPEG 2000 image processing capability existsConfirm that PDF viewing functionality is available in Chrome or that OpenJPEG-enabled image viewers/converters are installed (for example: 'file' command with libopenjpeg support, or PDF viewers using PDFium)Affected if PDF or JPEG 2000 image processing is possible in the environment, which enables the attack surface for this vulnerability
-
Check for presence of PDF files with embedded imagesUse 'find' command to locate PDF files on the system (for example: 'find /home -name "*.pdf" 2>/dev/null') or check browser download directoriesAffected if PDF files are present and could contain maliciously crafted JPEG 2000 images that trigger the overflow
The environment is affected if Google Chrome version is 52.0.2743.116 or lower, or if running OpenSUSE Leap 42.1 with OpenJPEG library present, and the system can process PDF files containing 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 53.0.2785.89 or later (Windows/OS X) or 53.0.2785.92 or later (Linux). For standalone OpenJPEG usage, update to a patched version that properly validates tile dimensions and prevents integer overflow in tile initialization.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing12.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,720.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5158 — 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-5158 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