dbcve.org
ChromeWeb browser · Google

CVE-2014-7947

MEDIUM · 5.0 CVSS v2.0 Published 2015-01-22
Fix available
A fix is available. Upgrade to after 40.0.2214.85 or later.
See remediation →
59/100
Remediation priority · Elevated
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
OpenJPEG before r2944, as used in PDFium in Google Chrome before 40.0.2214.91, allows remote attackers to cause a denial of service (out-of-bounds read) via a crafted PDF document, related to j2k.c, jp2.c, pi.c, t1.c, t2.c, and tcd.c.

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

Out-of-bounds read vulnerability in OpenJPEG library (versions before r2944) used by PDFium in Google Chrome before 40.0.2214.91. The flaw exists in multiple JPEG2000 parsing components (j2k.c, jp2.c, pi.c, t1.c, t2.c, tcd.c) and can be triggered by a crafted malicious PDF document, leading to denial of service.

MitigationUpdate Google Chrome to version 40.0.2214.91 or later to include the patched OpenJPEG library (r2944+). Ensure PDF rendering functionality works correctly after the update.

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

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

AV:N/AC:L/Au:N/C:N/I:N/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 installed Google Chrome version
    Navigate to chrome://settings/help or run 'google-chrome --version' in terminal to see the exact version number
    Affected if Version is 40.0.2214.85 or lower (any version up to and including 40.0.2214.85)
  2. Verify PDF rendering is enabled
    Navigate to chrome://settings/content and check PDF documents settings, or visit chrome://plugins to confirm the PDF viewer plugin is enabled
    Affected if PDF viewer plugin (PDFium) is enabled - the vulnerability only applies when the PDF rendering component is active
  3. Check for recent PDF handling activity
    Review Chrome's browsing history or downloaded files for any PDF documents opened in the affected Chrome version
    Affected if PDF files have been opened or downloaded using Chrome 40.0.2214.85 or lower - the vulnerability is triggered by parsing malicious JPEG2000 images within PDFs

You are affected if you are running Google Chrome version 40.0.2214.85 or lower with the PDF viewer enabled and have opened or could open untrusted PDF documents.

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 40.0.2214.85
Interim mitigation

Update Google Chrome to version 40.0.2214.91 or later to include the patched OpenJPEG library (r2944+). Ensure PDF rendering functionality works correctly after the update.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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