ChromeWeb browser · Google
CVE-2014-7945
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 · uneditedOpenJPEG before r2908, 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, and t2.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 confidenceOut-of-bounds read vulnerability in OpenJPEG (versions before r2908) when processing JPEG 2000 images in PDF documents via PDFium in Google Chrome versions before 40.0.2214.91. The vulnerability exists in j2k.c, jp2.c, and t2.c components, allowing remote attackers to cause a denial of service via a crafted PDF document.
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
<= 40.0.2214.85CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionNavigate to chrome://settings/help or use 'Help > About Google Chrome' to view the installed version numberAffected if Version is 40.0.2214.85 or earlier (versions before 40.0.2214.91 are affected)
-
Check if PDFium is used by another applicationIdentify if your application embeds Chrome's PDF viewer or uses PDFium library for rendering PDF documentsAffected if The application renders PDF documents containing JPEG 2000 images using a vulnerable PDFium/OpenJPEG combination
-
Identify direct OpenJPEG usageCheck application dependencies or libraries for OpenJPEG (libopenjpeg) usage - review build manifests, package dependencies, or library linkageAffected if Application links directly against OpenJPEG versions before r2908
-
Determine OpenJPEG version if used directlyFor linked OpenJPEG library, check version via library file properties, binary metadata, or query the library version export (such as openjpeg_version.h or opj_version function)Affected if OpenJPEG version is earlier than r2908 (commit hash or version number below that release)
You are affected if running Google Chrome version 40.0.2214.85 or earlier, or if using an application that embeds PDFium or links OpenJPEG earlier than r2908, and processing PDF documents 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 40.0.2214.91 or later. For applications using OpenJPEG directly, update to r2908 or later and rebuild/redeploy the affected software.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-7945 — 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-2014-7945 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