CVE-2015-5114
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 · uneditedUse-after-free vulnerability 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, a different vulnerability than CVE-2015-4448, CVE-2015-5095, CVE-2015-5099, CVE-2015-5101, CVE-2015-5111, and CVE-2015-5113.
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 confidenceUse-after-free vulnerability in Adobe Reader and Acrobat allows remote attackers to execute arbitrary code via unspecified vectors. The memory corruption occurs when the software attempts to access memory that has already been freed, potentially enabling 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.
-
Verify Adobe Reader installationCheck if AcroRd32.exe exists in typical installation paths such as C:\Program Files\Adobe\Reader XX.X\Reader\ or look for Adobe Reader in Add/Remove ProgramsAffected if Adobe Reader is installed on the system
-
Verify Adobe Acrobat installationCheck if Acrobat.exe exists in typical installation paths such as C:\Program Files\Adobe\Acrobat XX.X\Acrobat\ or look for Adobe Acrobat in Add/Remove ProgramsAffected if Adobe Acrobat is installed on the system
-
Obtain Adobe Reader versionRight-click on AcroRd32.exe, select Properties, then view the Product Version field in the Details tab. Alternatively, run: wmic product where "name like 'Adobe Reader%'" get name,versionAffected if The version displayed is 10.0 through 10.1.14, or 11.0.0 through 11.0.11, or 15.006.30033 through 15.006.30059, or 15.007.20033 through 15.008.20081
-
Obtain Adobe Acrobat versionRight-click on Acrobat.exe, select Properties, then view the Product Version field in the Details tab. Alternatively, run: wmic product where "name like 'Adobe Acrobat%'" get name,versionAffected if The version displayed is 10.0 through 10.1.14, or 11.0.0 through 11.0.11, or 15.006.30033 through 15.006.30059, or 15.007.20033 through 15.008.20081
You are affected if Adobe Reader or Adobe Acrobat is installed and the installed version falls within any of the affected ranges: 10.0 to 10.1.14, 11.0.0 to 11.0.11, 15.006.30033 to 15.006.30059, or 15.007.20033 to 15.008.20081.
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 to update Adobe Reader/Acrobat to versions 10.1.15 or later (10.x), 11.0.12 or later (11.x), 2015.006.30060 or later (DC Classic), or 2015.008.20082 or later (DC Continuous.
Adobe Acrobat/Reader 10.1.15, 11.0.12, DC Classic 2015.006.30060, or DC Continuous 2015.008.20082
- 1. Identify the exact Adobe product and version installed (Acrobat or Acrobat Reader, and which track: Classic or Continuous)
- 2. For Acrobat/Acrobat Reader 10.x: Upgrade to version 10.1.15 or later
- 3. For Acrobat/Acrobat Reader 11.x: Upgrade to version 11.0.12 or later
- 4. For Acrobat/Acrobat Reader DC Classic (2015 track): Upgrade to version 2015.006.30060 or later
- 5. For Acrobat/Acrobat Reader DC Continuous: Upgrade to version 2015.008.20082 or later
- 6. Download the appropriate updated version from the official Adobe website or use the built-in update mechanism
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5114 — 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-5114 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