dbcve.org
AcrobatApplication · Adobe

CVE-2015-6687

HIGH · 10.0 CVSS v2.0 Published 2015-10-14
Fix available
A fix is available. Upgrade to 15.006.30094 / 15.009.20069 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
Use-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.16 and 11.x before 11.0.13, Acrobat and Acrobat Reader DC Classic before 2015.006.30094, and Acrobat and Acrobat Reader DC Continuous before 2015.009.20069 on Windows and OS X allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-5586, CVE-2015-6683, CVE-2015-6684, CVE-2015-6688, CVE-2015-6689, CVE-2015-6690, CVE-2015-6691, CVE-2015-7615, CVE-2015-7617, and CVE-2015-7621.

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

Use-after-free vulnerability in Adobe Reader and Acrobat on Windows and OS X allowing arbitrary code execution. Affects versions 10.x before 10.1.16, 11.x before 11.0.13, and Acrobat/Reader DC versions before 2015.006.30094 (Classic) and 2015.009.20069 (Continuous).

MitigationUpdate Adobe Reader and Acrobat to versions 10.1.16, 11.0.13, or later for respective branches; for DC variants, apply patches 2015.006.30094 or 2015.009.20069 or later.

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.15>= 11.0.0, <= 11.0.12
Acrobat DcApplication
Affected:>= 15.006.30060, < 15.006.30094>= 15.008.20082, < 15.009.20069
Acrobat ReaderApplication
Affected:>= 10.0, <= 10.1.15>= 11.0.0, <= 11.0.12
Acrobat Reader DcApplication
Affected:>= 15.006.30060, < 15.006.30094>= 15.008.20082, < 15.009.20069

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 the installed Adobe product and version
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat or HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Reader, then check the Version or VersionMajor subkey. On Mac, right-click the application in /Applications and select Get Info to view the version.
    Affected if The version falls within the affected ranges: 10.0 to 10.1.15, 11.0.0 to 11.0.12, 15.006.30060 to 15.006.30093, or 15.008.20082 to 15.009.20068.
  2. Determine the product edition (Classic vs Continuous) for DC variants
    For DC versions, open the application and go to Help > About Adobe Acrobat DC (or Reader). The update version number displayed indicates the track. Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\FeatureState for the version string.
    Affected if The product is DC with version below 2015.006.30094 (Classic track) or below 2015.009.20069 (Continuous track).
  3. Verify the exact build number
    Open the application and go to Help > About Adobe Acrobat (or Reader). The full version string displayed includes the build number (for example, 15.006.30060). Compare this to the affected version ranges.
    Affected if The build number matches the vulnerable ranges: 15.006.30060-30093 or 15.008.20082-20068 for DC products.
  4. Check the product bitness on Windows
    Open Task Manager, locate the Acrobat or Reader process, right-click and select Properties. The Description tab shows whether it is a 32-bit or 64-bit process. This vulnerability affects both bitnesses on Windows and OS X.
    Affected if The product is running on Windows or OS X regardless of bitness, as the vulnerability applies to both platforms.

You are affected if your installed Adobe Acrobat or Reader version is 10.x through 10.1.15, 11.x through 11.0.12, DC Classic versions before 2015.006.30094, or DC Continuous versions before 2015.009.20069.

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.30094 / 15.009.20069 or later
Fixed in 15.006.3009415.009.20069
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Reader and Acrobat to versions 10.1.16, 11.0.13, or later for respective branches; for DC variants, apply patches 2015.006.30094 or 2015.009.20069 or later.

Recommended fix High confidence

Acrobat/Reader 10.x to 10.1.16; 11.x to 11.0.13; DC Classic to 2015.006.30094; DC Continuous to 2015.009.20069

  1. 1. Identify the current installed version of Adobe Acrobat or Adobe Reader from the Help > About menu
  2. 2. For Acrobat/Reader 10.x: Upgrade to version 10.1.16 or later
  3. 3. For Acrobat/Reader 11.x: Upgrade to version 11.0.13 or later
  4. 4. For Acrobat/Reader DC Classic: Upgrade to version 2015.006.30094 or later
  5. 5. For Acrobat/Reader DC Continuous: Upgrade to version 2015.009.20069 or later
  6. 6. Verify the update was successful by checking Help > About and confirming the version matches or exceeds the required fixed version
Caveat Standard Adobe update - may require restart and re-acceptance of license terms

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6687 — 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-6687 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