ChromeWeb browser · Google
CVE-2017-5057
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 58.0.3029.81 for Mac, Windows, and Linux, and 58.0.3029.83 for Android, allowed a remote attacker to perform an out of bounds memory read 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 component) allows a remote attacker to perform out-of-bounds memory reads via a specially crafted PDF file. The type confusion causes incorrect object handling during PDF parsing, leading to memory access beyond allocated boundaries.
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
< 58.0.3029.81< 58.0.3029.83
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 and navigate to chrome://version, or run 'google-chrome --version' or 'chrome --version' from command lineAffected if Version is earlier than 58.0.3029.81 (or 58.0.3029.83 for Android Chrome)
-
Confirm Chrome is the default PDF handlerOn Windows: Go to Default apps > Choose default apps by protocol > look for PDF entries. On Linux: Check system-wide or user-specific file associations for .pdf files using 'xdg-mime query default application/pdf'Affected if Chrome is set as the default application for opening PDF files
-
Verify PDF document handling is enabled in ChromeNavigate to chrome://settings in Chrome, scroll to Privacy and security section, click Additional content settings, verify PDF documents are not set to 'Open PDF files in Chrome' with download behavior changedAffected if PDF viewing in Chrome is enabled (this is the default setting)
-
Check for Chrome on Red Hat Enterprise Linux 6.0If running RHEL 6.0 desktop/workstation/server, check if Google Chrome is installed: 'rpm -qa | grep -i chrome' or 'yum list installed | grep -i chrome'Affected if Google Chrome is installed on RHEL 6.0 (the specific version range noted in the CVE)
You are affected if you have Google Chrome version earlier than 58.0.3029.81 installed AND use Chrome to open PDF files, particularly from untrusted sources.
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 data58.0.3029.8158.0.3029.83
Update Google Chrome to version 58.0.3029.81 or later (58.0.3029.83 for Android) to apply the vendor patch. Until updated, avoid opening untrusted PDF files in Chrome.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5057 — 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-5057 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