CVE-2017-3065
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 · uneditedAdobe Acrobat Reader versions 11.0.19 and earlier, 15.006.30280 and earlier, 15.023.20070 and earlier have an exploitable memory corruption vulnerability in the font manipulation functionality. Successful exploitation could lead to arbitrary code execution.
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 confidenceAdobe Acrobat Reader contains a memory corruption vulnerability in its font manipulation functionality. The vulnerability allows attackers to corrupt memory through specially crafted font files, potentially leading to arbitrary code execution.
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<= 11.0.19<= 15.006.30280<= 15.023.20070<= 15.006.30280<= 15.023.20070<= 11.0.19CVSS 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.0/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.
-
Identify the installed Adobe product and versionOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or Reader). Alternatively, on Windows check the program version in Add/Remove Programs or the registry key under HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\InstallPath. On macOS, right-click the application and select Get Info.Affected if The displayed version matches Adobe Acrobat, Adobe Acrobat DC, Adobe Acrobat Reader DC, or Adobe Reader and is at or below the affected version numbers.
-
Compare the version against affected rangesDocument the exact version number (for example, 11.0.19, 15.006.30280, or 15.023.20070). Compare it to the following thresholds: Adobe Acrobat/Reader 11.x versions at or below 11.0.19; Adobe Acrobat DC/Acrobat Reader DC Classic versions at or below 15.006.30280; Adobe Acrobat DC/Acrobat Reader DC Continuous versions at or below 15.023.20070.Affected if The installed version falls within or below any of these three version ranges.
-
Verify the vulnerability applies to this installationConfirm that the installation includes font handling capability. This vulnerability exists in the font manipulation functionality which is a core component of Adobe Acrobat and Reader - it is enabled by default in all standard installations.Affected if The installation is a standard Adobe Acrobat or Reader installation with default font handling features enabled.
A user is affected if they have Adobe Acrobat or Reader installed with a version at or below 11.0.19, 15.006.30280 (Classic), or 15.023.20070 (Continuous).
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 dataApply the appropriate security patches released by Adobe for Acrobat Reader. Users should update to versions 11.0.20 or later, 15.006.30291 or later, and 15.023.20080 or later.
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3065 — 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-3065 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