ChromeWeb browser · Google
CVE-2017-5108
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 · uneditedType confusion in PDFium in Google Chrome prior to 60.0.3112.78 for Mac, Windows, Linux, and Android allowed a remote attacker to potentially maliciously modify objects via a crafted PDF file.
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 confidenceType confusion vulnerability in PDFium, Google Chrome's PDF rendering engine, allowed a remote attacker to potentially modify objects through a maliciously crafted PDF file. This flaw could enable memory corruption leading to potential code execution. The vulnerability affected Chrome versions prior to 60.0.3112.78 on Mac, Windows, Linux, and Android platforms.
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
< 60.0.3112.78
Enterprise Linux DesktopOperating system
= 6.0
Enterprise Linux ServerOperating system
= 6.0
Enterprise Linux WorkstationOperating system
= 6.0CVSS 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.1/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 installed Google Chrome versionOpen Chrome, go to Settings > About Chrome, or navigate to chrome://settings/help. Alternatively, run 'google-chrome --version' or 'chrome --version' from command line.Affected if Version is earlier than 60.0.3112.78
-
Verify PDF viewing capability is enabledIn Chrome, go to chrome://settings and search for 'PDF' to confirm PDF viewer is not disabled, or check for the built-in PDF extension at chrome://extensions with 'PDF Viewer' enabled.Affected if PDF viewer is enabled and Chrome version is vulnerable
-
Check for Chrome packages on RHEL systemsOn Red Hat Enterprise Linux 6.0 systems, run 'rpm -qa | grep -i chrome' or 'yum list installed | grep -i chrome' to identify installed Chrome packages.Affected if Chrome is installed with version below 60.0.3112.78 on RHEL 6.0
-
Confirm PDFium is in useOpen any PDF file in Chrome or visit a page with embedded PDF content. PDFium is the internal PDF rendering engine and is automatically used when viewing PDFs in Chrome.Affected if PDFs are opened in Chrome and the browser version is affected
You are affected if Google Chrome version is below 60.0.3112.78 (or Chrome on RHEL 6.0) and the PDF viewer feature is enabled to handle PDF files.
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 data60.0.3112.78
Update Google Chrome to version 60.0.3112.78 or later. Organizations should deploy the patch through their standard patch management processes to ensure all endpoints receive the update.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5108 — 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-2017-5108 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