dbcve.org
ChromeWeb browser · Google

CVE-2014-7901

HIGH · 7.5 CVSS v2.0 Published 2014-11-19
Fix available
A fix is available. Upgrade to after 39.0.2171.45 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Integer overflow in the opj_t2_read_packet_data function in fxcodec/fx_libopenjpeg/libopenjpeg20/t2.c in OpenJPEG in PDFium, as used in Google Chrome before 39.0.2171.65, allows remote attackers to cause a denial of service or possibly have unspecified other impact via a long segment in a JPEG image.

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 overflow in the opj_t2_read_packet_data function in OpenJPEG (used by PDFium in Google Chrome) allows remote attackers to cause denial of service or possibly achieve unspecified impact via a specially crafted JPEG image with a long segment that triggers the overflow during packet data parsing.

MitigationUpdate Google Chrome to version 39.0.2171.65 or later. For embedded PDFium implementations, update the OpenJPEG library to the patched version that includes bounds checking in the opj_t2_read_packet_data function.

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:<= 39.0.2171.45

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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 menu to view the installed version number
    Affected if Version is 39.0.2171.45 or lower
  2. Confirm PDFium module is in use
    PDFium is the PDF rendering engine in Chrome that uses OpenJPEG; no additional check needed as this is enabled by default when Chrome processes JPEG images in PDF documents
    Affected if PDFium is processing any JPEG content (default behavior)
  3. Identify if OpenJPEG is used by any embedded application
    For non-Chrome environments using PDFium, inspect the application binaries or libraries for references to OpenJPEG (libopenjpeg) or the opj_t2_read_packet_data function
    Affected if Application uses a version of OpenJPEG prior to the patched version with bounds checking in opj_t2_read_packet_data

User is affected if running Google Chrome version 39.0.2171.45 or lower and processing a specially crafted JPEG image through PDFium.

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
Upgrade available Upgrade to a release after 39.0.2171.45
Interim mitigation

Update Google Chrome to version 39.0.2171.65 or later. For embedded PDFium implementations, update the OpenJPEG library to the patched version that includes bounds checking in the opj_t2_read_packet_data function.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,740
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-7901 — 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-2014-7901 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