CVE-2017-16367
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. This vulnerability is an instance of a type confusion overflow vulnerability. The vulnerability leads to an out of bounds memory access. Attackers can exploit the vulnerability by using the out of bounds access for unintended reads or writes -- potentially leading to code corruption, control-flow hijack, or an information leak attack.
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 confidenceThis is a type confusion vulnerability in Adobe Acrobat and Reader that allows attackers to trigger an out-of-bounds memory access condition. The vulnerability stems from improper type handling during PDF processing, leading to memory corruption that can be leveraged for code execution, control-flow hijacking, or information disclosure.
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 productOpen Adobe Acrobat or Reader, go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Alternatively, check Programs and Features (Windows) or Applications folder (Mac) for the installed Adobe product name and version.Affected if The installed product is Adobe Acrobat or Adobe Reader (or their DC variants)
-
Determine exact version numberLocate the full version string (e.g., 11.0.22, 17.011.30066, 15.006.30355) as shown in the About dialog or installed programs list.Affected if Version cannot be determined or is unclear
-
Compare version against affected ranges for standard Acrobat/ReaderFor Adobe Acrobat or Adobe Acrobat Reader (non-DC), check if version is <= 11.0.22 OR falls between 17.0 and 17.011.30066 inclusive.Affected if Version matches <= 11.0.22 or is >= 17.0 through <= 17.011.30066
-
Compare version against affected ranges for DC variantsFor Adobe Acrobat DC or Adobe Acrobat Reader DC, check if version is <= 17.012.20098 OR falls between 15.0 and 15.006.30355 inclusive.Affected if Version matches <= 17.012.20098 or is >= 15.0 through <= 15.006.30355
If the installed Adobe Acrobat or Reader version falls within any of the affected version ranges listed, the environment is vulnerable to this type confusion flaw.
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 relevant Adobe security updates for Acrobat and Reader (refer to APSB17-36) to remediate this vulnerability in all affected versions.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-16367 — 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-16367 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