CVE-2015-5093
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 · uneditedBuffer overflow in Adobe Reader and Acrobat 10.x before 10.1.15 and 11.x before 11.0.12, Acrobat and Acrobat Reader DC Classic before 2015.006.30060, and Acrobat and Acrobat Reader DC Continuous before 2015.008.20082 on Windows and OS X allows attackers to execute arbitrary code via unspecified vectors.
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 overflow vulnerability in Adobe Reader and Acrobat (multiple versions) on Windows and OS X allows remote attackers to execute arbitrary code via unspecified vectors. The flaw enables memory corruption leading 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>= 10.0, < 10.1.15>= 11.0.0, < 11.0.12>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082>= 10.0, < 10.1.15>= 11.0.0, < 11.0.12>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082CVSS 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
- Authentication
- None
- Confidentiality
- Complete
- Integrity
- Complete
- Availability
- Complete
AV:N/AC:L/Au:N/C:C/I:C/A:C
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). Note the exact product name shown (Acrobat, Acrobat Reader, Acrobat DC, or Acrobat Reader DC).Affected if Any Adobe Acrobat or Reader product is installed.
-
Determine exact version numberIn the About dialog, record the full version number shown (for example: 10.1.14, 11.0.11, 15.006.30033, 15.007.20033).Affected if Version is displayed and can be compared against affected ranges.
-
Compare classic version to affected rangesFor Acrobat/Reader (non-DC): compare to 10.0 through 10.1.14 (vulnerable) and 11.0.0 through 11.0.11 (vulnerable). For DC: compare to 15.006.30033 through 15.006.30059 (vulnerable) and 15.007.20033 through 15.008.20081 (vulnerable).Affected if Version falls within any of these ranges: 10.0 to <10.1.15, 11.0.0 to <11.0.12, 15.006.30033 to <15.006.30060, or 15.007.20033 to <15.008.20082.
-
Verify DC track type (if DC version)For DC versions, check if the update track is Classic or Continuous by going to Help > Check for Updates, or check the version string pattern (15.006.xxxx is Classic, 15.007.xxxx is Continuous).Affected if DC version is installed and matches vulnerable ranges.
You are affected if Adobe Acrobat or Reader is installed and the version number falls within any of the four vulnerable ranges listed 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 · scoped10.1.1511.0.1215.006.30060
Apply vendor-supplied patches: update to Adobe Reader/Acrobat 10.1.15+, 11.0.12+, Classic 2015.006.30060+, or Continuous 2015.008.20082+ to remediate.
Adobe Acrobat/Reader 10.1.15, 11.0.12, DC Classic 15.006.30060, or DC Continuous 15.008.20082 (or later) depending on product and track
- 1. Identify the currently installed Adobe Acrobat or Adobe Reader version on the system.
- 2. Based on the product type (Acrobat or Acrobat Reader) and track (Classic or Continuous), determine the minimum safe version needed: For versions 10.x, upgrade to 10.1.15 or later; For versions 11.x, upgrade to 11.0.12 or later; For Acrobat/Reader DC Classic (15.xxxx before 15.006.30060), upgrade to 15.006.30060 or later; For Acrobat/Reader DC Continuous (15.xxxx before 15.008.20082), upgrade to
- 3. Download the appropriate updated version from the official Adobe website or your organization's software distribution point.
- 4. Close all running instances of Adobe Acrobat or Adobe Reader before installing the update.
- 5. Apply the security update or install the new version.
- 6. Verify the installed version matches the expected fixed version after installation.
- 7. Test that PDF files open and function normally in the updated application.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5093 — 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-2015-5093 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