dbcve.org
AcrobatApplication · Adobe

CVE-2015-6684

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-6687, 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 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 code injection and execution.

MitigationApply vendor-supplied patches (10.1.16, 11.0.13, 2015.006.30094, or 2015.009.20069 depending on product line) or upgrade to the latest Adobe Reader/Acrobat version.

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
    Open Adobe Reader or Adobe Acrobat, then go to Help > About Adobe Reader (or About Adobe Acrobat) to see the exact product name and version number
    Affected if The product is Adobe Reader or Adobe Acrobat (Classic or DC variant) on Windows or OS X
  2. Determine the product variant
    Check if the installation is Adobe Acrobat/Reader Classic or Acrobat/Reader DC (the 2015 prefix in version numbers indicates DC variant)
    Affected if The product is either Classic (versions 10.x or 11.x) or DC (versions starting with 15.x)
  3. Check Classic version for 10.x branch
    If version starts with 10., compare the full version number against 10.0 through 10.1.15 (vulnerable) versus 10.1.16 and later (fixed)
    Affected if The installed version is 10.0 through 10.1.15 inclusive
  4. Check Classic version for 11.x branch
    If version starts with 11., compare the full version number against 11.0.0 through 11.0.12 (vulnerable) versus 11.0.13 and later (fixed)
    Affected if The installed version is 11.0.0 through 11.0.12 inclusive
  5. Check DC version for 15.006 branch
    If version starts with 15.006., compare against 15.006.30060 through 15.006.30093 (vulnerable) versus 15.006.30094 and later (fixed)
    Affected if The installed version is 15.006.30060 through 15.006.30093 inclusive
  6. Check DC version for 15.008/15.009 branch
    If version starts with 15.008. or 15.009., compare against 15.008.20082 through 15.009.20068 (vulnerable) versus 15.009.20069 and later (fixed)
    Affected if The installed version is 15.008.20082 through 15.009.20068 inclusive

The environment is affected if Adobe Reader or Acrobat (Classic or DC) is installed with a version number falling within any of the vulnerable ranges: 10.0-10.1.15, 11.0.0-11.0.12, 15.006.30060-15.006.30093, or 15.008.20082-15.009.20068.

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

Apply vendor-supplied patches (10.1.16, 11.0.13, 2015.006.30094, or 2015.009.20069 depending on product line) or upgrade to the latest Adobe Reader/Acrobat version.

Recommended fix High confidence

Adobe Acrobat/Reader 10.1.16 (10.x), 11.0.13 (11.x), 2015.006.30094 (DC Classic), 2015.009.20069 (DC Continuous)

  1. 1. Identify the currently installed Adobe Acrobat or Adobe Reader version by opening the application, clicking Help > About (or on Mac, Acrobat/Reader > About Adobe Acrobat/Reader)
  2. 2. Based on the installed version, download the corresponding patched version from Adobe's official download page or your organization's software distribution channel
  3. 3. For Adobe Acrobat/Reader 10.x: Upgrade to version 10.1.16 or later
  4. 4. For Adobe Acrobat/Reader 11.x: Upgrade to version 11.0.13 or later
  5. 5. For Adobe Acrobat/Reader DC Classic: Upgrade to version 2015.006.30094 or later (build 2015.006.30094)
  6. 6. For Adobe Acrobat/Reader DC Continuous: Upgrade to version 2015.009.20069 or later (build 2015.009.20069)
  7. 7. Close all Adobe applications before installing the update
  8. 8. Run the installer with appropriate administrative privileges
Caveat Standard Adobe update - minimal risk; ensure to back up any custom preferences or plugins if applicable

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,360
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,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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