CVE-2017-16365
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 · uneditedAn issue was discovered in Adobe Acrobat and Reader: 2017.012.20098 and earlier versions, 2017.011.30066 and earlier versions, 2015.006.30355 and earlier versions, and 11.0.22 and earlier versions. The vulnerability is caused by a buffer over-read in the True Type2 Font parsing module. A corrupted cmap table input leads to a computation where the pointer arithmetic results in a location outside valid memory locations belonging to the buffer. An attack can be used to obtain sensitive information, such as object heap addresses, etc.
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 confidenceBuffer over-read vulnerability in Adobe Acrobat and Reader's True Type2 Font parsing module. A corrupted cmap table in embedded fonts triggers incorrect pointer arithmetic, allowing reads outside buffer boundaries and leakage of sensitive memory information like heap addresses.
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.22>= 17.0, <= 17.011.30066>= -, <= 17.012.20098>= 15.0, <= 15.006.30355<= 11.0.22>= 17.0, <= 17.011.30066>= -, <= 17.012.20098>= 15.0, <= 15.006.30355CVSS 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.0/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.
-
Identify installed Adobe product and variantOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or Reader) to see which product (Acrobat/Reader) and variant (Classic/Acrobat DC/Reader DC) is installed.Affected if The product is Adobe Acrobat or Reader in any variant.
-
Determine the installed version numberIn the About dialog, note the exact version number displayed (for example, 11.0.22 or 17.011.30066).Affected if A version number is displayed.
-
Check version against affected ranges for Acrobat ClassicFor Adobe Acrobat (Classic): versions <= 11.0.22 OR >= 17.0 through 17.011.30066 are affected. Compare your version to these ranges.Affected if Your Acrobat version is 11.0.22 or lower, OR between 17.0 and 17.011.30066 inclusive.
-
Check version against affected ranges for Acrobat DCFor Adobe Acrobat DC: versions >= 15.0 through 15.006.30355 OR <= 17.012.20098 are affected. Compare your version to these ranges.Affected if Your Acrobat DC version is between 15.0 and 15.006.30355 inclusive, OR 17.012.20098 or lower.
-
Check version against affected ranges for Reader ClassicFor Adobe Reader (Classic): versions <= 11.0.22 OR >= 17.0 through 17.011.30066 are affected. Compare your version to these ranges.Affected if Your Reader version is 11.0.22 or lower, OR between 17.0 and 17.011.30066 inclusive.
-
Check version against affected ranges for Reader DCFor Adobe Reader DC: versions >= 15.0 through 15.006.30355 OR <= 17.012.20098 are affected. Compare your version to these ranges.Affected if Your Reader DC version is between 15.0 and 15.006.30355 inclusive, OR 17.012.20098 or lower.
You are affected if your installed Adobe Acrobat or Reader version falls within any of the specified vulnerable ranges, and you open PDF files containing a corrupted cmap table in embedded fonts.
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 Adobe Acrobat and Reader to patched versions (2018.009.20050, 2017.011.30070, 2015.006.30417, 11.0.23 or later). Avoid opening untrusted PDF files from unknown sources until updates are applied.
- 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-16365 — 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-16365 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