dbcve.org
ChromeWeb browser · Google

CVE-2015-1359

MEDIUM · 6.8 CVSS v2.0 Published 2015-01-27
Fix available
A fix is available. Upgrade to after 40.0.2214.85 or later.
See remediation →
77/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
Multiple off-by-one errors in fpdfapi/fpdf_font/font_int.h in PDFium, as used in Google Chrome before 40.0.2214.91, allow remote attackers to cause a denial of service (buffer overflow) or possibly have unspecified other impact via a crafted PDF document, related to an "intra-object-overflow" issue, a different vulnerability than CVE-2015-1205.

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

Off-by-one errors in PDFium's font handling code (fpdfapi/fpdf_font/font_int.h) allow buffer overflows when parsing crafted PDF documents with malformed font data. This intra-object-overflow can cause denial of service or potentially execute arbitrary code.

MitigationUpdate Google Chrome to version 40.0.2214.91 or later, or update PDFium library to patched version addressing the font boundary check vulnerabilities in font_int.h.

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

AV:N/AC:M/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. Verify Google Chrome is installed
    Check for Chrome installation in typical locations: %PROGRAMFILES%\Google\Chrome\Application\chrome.exe (Windows), /Applications/Google Chrome.app (macOS), or /usr/bin/google-chrome (Linux)
    Affected if Chrome browser is present on the system
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://version, or right-click the Chrome shortcut and select Properties to view the version in the Target field, or run 'google-chrome --version' from command line
    Affected if Version displayed is 40.0.2214.85 or lower
  3. Confirm PDFium usage is possible
    Verify Chrome has PDF viewing capability enabled - check chrome://plugins for the Chrome PDF Viewer plugin is not disabled
    Affected if PDF viewing is enabled and the browser can process PDF documents

User is affected if Google Chrome version is 40.0.2214.85 or lower and PDF viewing is enabled, allowing processing of potentially malicious PDF files with malformed font data.

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, or update PDFium library to patched version addressing the font boundary check vulnerabilities in font_int.h.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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