CVE-2017-11308
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 and Reader versions 2017.012.20098 and earlier, 2017.011.30066 and earlier, 2015.006.30355 and earlier, 11.0.22 and earlier have an exploitable heap overflow vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.
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 heap overflow vulnerability in Adobe Acrobat and Reader allows attackers to corrupt heap memory and achieve arbitrary code execution in the context of the current user by specially crafting malicious PDF documents.
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.0, <= 11.0.22>= 17.011.30066, < 17.011.30068>= 15.006.30355, < 15.006.30392>= 17.012.20098, < 18.009.20044>= 11.0.0, <= 11.0.22>= 17.011.30066, < 17.011.30068>= 15.006.30355, < 15.006.30392>= 17.012.20098, < 18.009.20044CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 if Adobe Acrobat or Reader is installedOn Windows, open Control Panel > Programs and Features and look for Adobe Acrobat or Adobe Acrobat Reader. On macOS, check /Applications for Adobe Acrobat or Adobe Reader.Affected if Either Adobe Acrobat or Adobe Reader is present on the system
-
Check the installed product versionIn Windows: Open Adobe Acrobat/Reader, go to Help > About Adobe Acrobat/Reader to see the version number. Alternatively, check the registry key at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\InstallPath or similar. On macOS, right-click the app in Applications and select Get Info to view the version.Affected if The version displayed matches any of the vulnerable version ranges listed in the CVE
-
Compare your version against affected rangesMatch your installed version to these vulnerable ranges: Acrobat/Reader 11.0.0 through 11.0.22; versions 17.011.30066 through 17.011.30067; Acrobat/Reader Dc 15.006.30355 through 15.006.30391; versions 17.012.20098 through 18.009.20043. These versions are all affected.Affected if Your installed version falls within any of these ranges: 11.0.0-11.0.22, 17.011.30066-17.011.30067, 15.006.30355-15.006.30391, or 17.012.20098-18.009.20043
You are affected if Adobe Acrobat or Reader is installed and the version number matches any of the vulnerable ranges specified in the CVE.
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.
dbcve · scoped15.006.3039217.011.3006818.009.20044
Update Adobe Acrobat and Reader to versions beyond 2017.012.20098, 2017.011.30066, 2015.006.30355, and 11.0.22 respectively, or apply the vendor-supplied patches.
Adobe Acrobat/Reader DC Continuous track: 18.009.20044 or later; Classic track: 15.006.30392 or later; 2017 track: 17.011.30068 or later; 11.x: 11.0.23 or later (migrate to newer version preferred)
- 1. Determine the exact version of Adobe Acrobat or Reader installed by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. For Acrobat/Reader 11.x (version 11.0.22 and earlier): Upgrade to the latest version 11.0.23 or later, though Adobe no longer supports this version line and migration to newer versions is recommended.
- 3. For Acrobat/Reader DC Classic track (version 15.006.30355 and earlier): Upgrade to version 15.006.30392 or later.
- 4. For Acrobat/Reader DC Continuous track (version 17.012.20098 and earlier): Upgrade to version 18.009.20044 or later.
- 5. For Acrobat/Reader 2017 track (version 17.011.30066 and earlier): Upgrade to version 17.011.30068 or later.
- 6. Download the appropriate update from the official Adobe security bulletin at helpx.adobe.com/security/products/acrobat/apsb17-24.html
- 7. Close all Adobe applications before applying the update.
- 8. Run the downloaded installer and follow the prompts to complete the installation.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11308 — 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-11308 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