CVE-2017-11307
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 out-of-bounds read 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 confidenceAdobe Acrobat and Reader contain an out-of-bounds read vulnerability that allows reading memory beyond allocated boundaries. Successful exploitation enables arbitrary code execution in the context of the current user, typically achieved by tricking users into opening maliciously crafted PDF files.
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 installed Adobe productOpen Adobe Acrobat or Reader, go to Help > About Adobe Acrobat (or Reader) to see the exact version number displayed in the product window.Affected if The installed product is Adobe Acrobat or Adobe Acrobat Reader (any version)
-
Check Windows Registry for versionOpen Registry Editor and navigate to HKLM\SOFTWARE\Adobe\Adobe Acrobat\ (or HKLM\SOFTWARE\Adobe\Adobe Acrobat Reader\) and examine the Version or VersionNumber subkey under the installed version folder (e.g., 11.0, 15.0, 17.0).Affected if The product is installed and version information is found in the Registry
-
Compare version to affected rangesMatch your installed version against these vulnerable ranges: Acrobat/Reader 11.0.0 through 11.0.22; versions 17.011.30066 up to 17.011.30067; versions 15.006.30355 through 15.006.30391; versions 17.012.20098 through 18.009.20043.Affected if Your installed version falls within any of the listed vulnerable ranges
-
Verify Reader DC variant versionIf using Adobe Acrobat Reader DC, check the version under HKLM\SOFTWARE\Adobe\Adobe Acrobat Reader\DC\InstallPath or via Help > About Adobe Acrobat Reader DC.Affected if Reader DC version is between 15.006.30355 and 15.006.30391, or between 17.012.20098 and 18.009.20043
-
Check for automatic updatesOpen the product, go to Help > Check for Updates or navigate to Edit > Preferences > Updater to see if updates are configured and what version they report as available.Affected if The available update version is higher than your current vulnerable version, indicating you are on a patched version
You are affected if Adobe Acrobat or Reader is installed and the version number falls within any of the vulnerable 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.
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 newer than those listed (2017.012.20098, 2017.011.30066, 2015.006.30355, 11.0.22) by downloading patches from Adobe's official security bulletin. Consider restricting PDF handling from untrusted sources until patches are applied.
Acrobat/Reader 11.0.23+; Acrobat/Reader 15.006.30392+; Acrobat/Reader 17.011.30068+; Acrobat/Reader DC 18.009.20044+
- 1. Identify the current installed version of Adobe Acrobat or Adobe Reader from the Help > About menu
- 2. For Acrobat/Reader 11.x (classic): Upgrade to version 11.0.23 or later
- 3. For Acrobat/Reader 15.x (2015): Upgrade to version 15.006.30392 or later
- 4. For Acrobat/Reader 17.x (2017): Upgrade to version 17.011.30068 or later for the 17.011 branch, or version 18.009.20044 or later for the 17.012 branch
- 5. For Acrobat/Reader DC (continuous): Upgrade to version 18.009.20044 or later
- 6. Download the latest version from the official Adobe website or use the Adobe Acrobat auto-update feature
- 7. Verify the installation by checking Help > About to confirm the version number matches the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11307 — 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-11307 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