CVE-2015-5094
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 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 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2015-3095, CVE-2015-5087, CVE-2015-5100, CVE-2015-5102, CVE-2015-5103, CVE-2015-5104, and CVE-2015-5115.
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 confidenceMemory corruption vulnerability in Adobe Reader and Acrobat on Windows and OS X allowing arbitrary code execution or denial of service. The attack vector involves unspecified vectors, likely malicious PDF files, enabling attackers to achieve remote code execution through memory manipulation.
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 the installed Adobe productOpen Adobe Reader or Acrobat, then go to Help > About Adobe Reader (or Acrobat) to see the exact product name and version numberAffected if The product is Adobe Acrobat, Adobe Acrobat Dc, Adobe Acrobat Reader, or Adobe Acrobat Reader Dc
-
Determine the exact version numberNote the full version number displayed in the About dialog (for example, 10.1.14 or 15.006.30033)Affected if The version falls within any of the vulnerable ranges
-
Compare against vulnerable version rangesMatch your version against these vulnerable ranges: Acrobat/Reader 10.x < 10.1.15; 11.x < 11.0.12; DC Classic < 15.006.30060; DC Continuous < 15.008.20082Affected if Your installed version is lower than the first safe version in any of these ranges
-
Confirm the product platformVerify the installation is on Windows or OS X as listed in the CVE scopeAffected if The affected platform is Windows or OS X
You are affected if Adobe Reader or Acrobat is installed on Windows or OS X with a version matching the vulnerable ranges: 10.x before 10.1.15, 11.x before 11.0.12, DC Classic before 15.006.30060, or DC Continuous before 15.008.20082.
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 patches by updating to Adobe Reader/Acrobat 10.1.15+, 11.0.12+, Classic 2015.006.30060+, or Continuous 2015.008.20082+. Consider disabling JavaScript in Adobe Reader settings as an additional hardening measure.
Acrobat/Reader 10.x to 10.1.15+; Acrobat/Reader 11.x to 11.0.12+; Acrobat/Reader DC Classic to 2015.006.30060+; Acrobat/Reader DC Continuous to 2015.008.20082+
- 1. Identify the exact version of Adobe Acrobat or Adobe Reader currently installed by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. Determine the product track: Classic (10.x or 11.x) or DC (Continuous or Classic).
- 3. For Acrobat/Reader 10.x: upgrade to version 10.1.15 or later.
- 4. For Acrobat/Reader 11.x: upgrade to version 11.0.12 or later.
- 5. For Acrobat/Reader DC Classic (15.006.x branch): upgrade to version 15.006.30060 or later.
- 6. For Acrobat/Reader DC Classic (15.007.x branch): upgrade to version 15.008.20082 or later.
- 7. Download the appropriate fixed version from the official Adobe security bulletin at https://helpx.adobe.com/security/products/reader/apsb15-15.html
- 8. Close all Adobe applications before running the installer.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5094 — 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-5094 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