ChromeWeb browser · Google
CVE-2016-5152
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 · uneditedInteger overflow in the opj_tcd_get_decoded_tile_size 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, allows 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 in opj_tcd_get_decoded_tile_size in OpenJPEG's tcd.c allows attackers to trigger heap-based buffer overflows via crafted JPEG 2000 image data. The overflow occurs when the function calculates decoded tile sizes without proper integer overflow checks, leading to undersized buffer allocations that can be overflown.
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 use 'About Google Chrome' to view the installed version numberAffected if Version is 52.0.2743.116 or earlier
-
Check OpenJPEG library version on OpenSuse Leap 42.1Run 'rpm -qi openjpeg' or 'dpkg -l libopenjpeg*' to query the installed OpenJPEG package versionAffected if OpenJPEG library version corresponds to the package bundled with OpenSuse Leap 42.1 and is unpatched
-
Identify applications using OpenJPEG for JPEG 2000 processingSearch for executables or libraries that link to OpenJPEG: 'ldd /path/to/binary | grep openjpeg' or check for j2k, jp2, j2c file handlers in image processing softwareAffected if Applications process JPEG 2000 (.j2k, .jp2, .j2c) files using vulnerable OpenJPEG code
-
Determine if JPEG 2000 image processing occursReview application logs or audit file access for .j2k, .jp2, .j2c file types being opened or decodedAffected if The environment processes untrusted JPEG 2000 images through the affected OpenJPEG code path in tcd.c
User is affected if they run Chrome version 52.0.2743.116 or earlier on OpenSuse Leap 42.1 with unpatched OpenJPEG, and process crafted JPEG 2000 images through the vulnerable opj_tcd_get_decoded_tile_size function.
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 embedded applications using OpenJPEG directly, apply vendor patches that add bounds checking and integer overflow validation in the tile size calculation routines.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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 $5,536.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5152 — 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-5152 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