ChromeWeb browser · Google
CVE-2017-5039
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 · uneditedA use after free in PDFium in Google Chrome prior to 57.0.2987.98 for Mac, Windows, and Linux and 57.0.2987.108 for Android allowed a remote attacker to potentially exploit heap corruption 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 confidenceA use-after-free vulnerability in PDFium (Google Chrome's PDF rendering engine) allows a remote attacker to trigger heap corruption via a specially crafted PDF file. The vulnerability exists because the code continues to access memory after it has been freed, leading to potential exploitation of heap metadata corruption.
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
<= 57.0.2987.75<= 57.0.2987.100
Debian LinuxOperating system
= 8.0= 9.0
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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 Google Chrome version on Windows or macOSOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' from command lineAffected if Version is 57.0.2987.75 or earlier, or falls between 57.0.2987.76 and 57.0.2987.100 inclusive
-
Check installed Chrome package on Debian LinuxRun 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable'Affected if Installed version is 57.0.2987.75 or earlier, or the candidate version shows 57.0.2987.100 or earlier
-
Check installed Chrome package on RHEL/CentOSRun 'rpm -qa | grep chrome' or 'yum list installed google-chrome-stable'Affected if Installed version corresponds to 57.0.2987.75 or earlier, or shows 57.0.2987.100 or earlier
-
Verify PDFium is accessibleAttempt to open any PDF file in Chrome, or check if Chrome is configured as a PDF handler in the systemAffected if PDF files can be opened in Chrome and the Chrome version is within the affected range
-
Compare installed version against affected rangesCompare your found version number to the affected ranges: <=57.0.2987.75 or <=57.0.2987.100Affected if Your installed version is equal to or lower than 57.0.2987.75, or between 57.0.2987.76 and 57.0.2987.100 inclusive
You are affected if Chrome with a version at or below 57.0.2987.75 or within 57.0.2987.76-57.0.2987.100 is installed and can be used to open 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 dataUpdate Google Chrome to version 57.0.2987.98 or later (57.0.2987.108 for Android) to patch the vulnerability. In enterprise environments, use centralized patch management to deploy the update and verify successful installation.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5039 — 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-5039 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