dbcve.org
AcrobatApplication · Adobe

CVE-2015-5087

HIGH · 10.0 CVSS v2.0 Published 2015-07-15
Fix available
A fix is available. Upgrade to 15.006.30060 / 15.008.20082 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
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 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-5094, 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 confidence

Memory corruption vulnerability in Adobe Reader and Acrobat allows remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. Affects versions 10.x before 10.1.15, 11.x before 11.0.12, and Acrobat DC versions before 2015.006.30060 (Classic) and 2015.008.20082 (Continuous) on Windows and OS X.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.15, 11.0.12, or later. Until patched, disable JavaScript in Adobe Reader settings and implement network-level controls to block suspicious 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
AcrobatApplication
Affected:>= 10.0, <= 10.1.14>= 11.0.0, <= 11.0.11
Acrobat DcApplication
Affected:>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082
Acrobat ReaderApplication
Affected:>= 10.0, <= 10.1.14>= 11.0.0, <= 11.0.11
Acrobat Reader DcApplication
Affected:>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Adobe product and version on Windows
    Open the application and go to Help > About Adobe Acrobat (or Adobe Acrobat Reader). Alternatively, check the Windows Registry under HKLM\SOFTWARE\Adobe\Adobe Acrobat\ or HKLM\SOFTWARE\Adobe\Adobe Acrobat Reader\ for the Version key.
    Affected if The displayed version falls within any of the affected ranges: 10.0-10.1.14, 11.0.0-11.0.11, 15.006.30033-15.006.30059 (Classic), or 15.007.20033-15.008.20081 (Continuous).
  2. Determine if running Acrobat DC Classic or Continuous track
    In the application, go to Help > Check for Updates or view the version string. Classic track versions contain 15.006.xxxx while Continuous track versions contain 15.007.xxxx or 15.008.xxxx.
    Affected if The version is a DC release (15.x) and the track cannot be determined, making version comparison ambiguous for DC releases.
  3. Verify OS platform is Windows or OS X
    Confirm the operating system is either Windows or OS X. On macOS, check the application bundle info or use About This Mac.
    Affected if The affected product is running on Windows or OS X, as this CVE only applies to those platforms.
  4. Confirm JavaScript availability in PDF handler
    In Adobe Reader/Acrobat, go to Edit > Preferences > JavaScript and verify if JavaScript is enabled. This is not required for exploitation but is a common attack vector for PDF vulnerabilities.
    Affected if JavaScript is enabled in the PDF viewer settings (though the CVE specifies unspecified vectors, not specifically JavaScript).

You are affected if Adobe Acrobat or Adobe Acrobat Reader is installed with a version between 10.0 and 10.1.14, between 11.0.0 and 11.0.11, or between 15.006.30033 and 15.006.30059 (Classic track) or between 15.007.20033 and 15.008.20081 (Continuous track) on Windows or OS X.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 15.006.30060 / 15.008.20082 or later
Fixed in 15.006.3006015.008.20082
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Reader and Acrobat to version 10.1.15, 11.0.12, or later. Until patched, disable JavaScript in Adobe Reader settings and implement network-level controls to block suspicious PDF files.

Recommended fix High confidence

Acrobat/Reader 10.x -> 10.1.15; Acrobat/Reader 11.x -> 11.0.12; Acrobat/Reader DC Classic -> 15.006.30060 or later; Acrobat/Reader DC Continuous -> 15.008.20082 or later

  1. Identify which Adobe product line and version is currently installed (Acrobat/Reader, version 10.x, 11.x, or DC Classic/Continuous)
  2. For Acrobat/Reader 10.x: Download and install version 10.1.15 from Adobe's official website or your organization's software distribution channel
  3. For Acrobat/Reader 11.x: Download and install version 11.0.12 from Adobe's official website or your organization's software distribution channel
  4. For Acrobat/Reader DC Classic: Update to version 15.006.30060 or later via Adobe's automatic updater or manual download
  5. For Acrobat/Reader DC Continuous: Update to version 15.008.20082 or later via Adobe's automatic updater or manual download
  6. Verify the installed version matches the target fixed version after installation
  7. Restart the application and confirm it launches without errors
Caveat Adobe updates are generally safe; enterprise deployments should test compatibility with existing PDF workflows and plugins before broad rollout

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-5087 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-5087 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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