CVE-2017-11293
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. An exploitable memory corruption vulnerability exists. 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 · moderate confidenceMemory corruption vulnerability in Adobe Acrobat and Reader allowing arbitrary code execution. The vulnerability exists in multiple older versions across 2015, 2017, and 11.x product lines. Successful exploitation could lead to complete system compromise.
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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/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 productCheck for Adobe Acrobat or Adobe Acrobat Reader installation. Look in Program Files (Windows) or Applications (Mac) for folders named 'Adobe Acrobat' or 'Adobe Reader'. The product name appears in the application title bar when launched.Affected if Any version of Adobe Acrobat or Adobe Acrobat Reader is installed
-
Determine exact version numberIn Windows: Right-click the executable (Acrobat.exe or Acrord32.exe), select Properties, and check the Version tab. Or open the application, go to Help > About Adobe Acrobat/Reader. In macOS: Right-click the app in Applications, select Get Info, or open the app and go to Adobe Acrobat/Reader > About.Affected if The installed version matches the affected ranges
-
Identify the product track (Desktop or Continuous)For Acrobat/Reader DC: Check if it is the Continuous track (updates automatically) or Desktop track (manual updates). This is visible in Help > Check for Updates or in the application title (often 'Acrobat DC' vs 'Acrobat 2017' or 'Acrobat XI'). The version number format differs: Continuous uses 17.xxxxx.xxxx, Desktop/2017 uses 17.x.xxxx, XI uses 11.x.xx.Affected if The track version falls within the affected ranges for that specific track
-
Compare version against affected rangesMatch your installed version to these ranges: Acrobat/Reader XI: <= 11.0.22; Acrobat/Reader 2017 (Desktop): >= 17.0, <= 17.011.30066; Acrobat/Reader DC Continuous: <= 17.012.20098; Acrobat/Reader DC (Classic): >= 15.0, <= 15.006.30355Affected if Installed version is at or below the upper bound AND above any stated minimum of the applicable range
If Adobe Acrobat or Reader is installed and the version number falls within any of the affected ranges (11.0.22 or below, 17.x up to 17.011.30066, 17.012.20098, or 15.x up to 15.006.30355 depending on product track), the environment is vulnerable to CVE-2017-11293.
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 · scopedApply Adobe security updates to patch to versions later than 2017.012.20098, 2017.011.30066, 2015.006.30355, and 11.0.22. Prioritize patching given the critical CVSS score and potential for remote exploitation.
Acrobat/Reader 2017 (18.x): upgrade to 18.011.20063 or later | Acrobat/Reader 2015 (15.x): upgrade to 15.006.30356 or later | Acrobat/Reader 11.x: upgrade to 11.0.23 or later
- 1. Open Adobe Acrobat or Adobe Acrobat Reader on the affected system
- 2. Navigate to Help > Check for Updates (or Help > About Adobe Acrobat Reader)
- 3. Download and install the latest available security update from Adobe
- 4. Alternatively, download the security update manually from Adobe's security bulletins page (helpx.adobe.com/security/products/acrobat/apsb17-21.html)
- 5. Restart the application after the update completes
- 6. Verify the installed version matches or exceeds the fixed release (18.011.20063 for 2017 track, 15.006.30356 or later for 2015 track, or 11.0.23 or later for 11.x track)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-11293 — 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-11293 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