CVE-2015-6683
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.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-6684, 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 confidenceUse-after-free vulnerability in Adobe Reader and Acrobat allows remote attackers to execute arbitrary code via unspecified vectors. The flaw involves improper memory management where the software attempts to access memory that has already been freed, leading to potential code execution.
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.30060, < 15.006.30094>= 15.008.20082, < 15.009.20069>= 10.0, <= 10.1.15>= 11.0.0, <= 11.0.12>= 15.006.30060, < 15.006.30094>= 15.008.20082, < 15.009.20069CVSS 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 installed Adobe PDF productOpen the application and go to Help > About Adobe Acrobat Reader or About Adobe Acrobat, or on Windows check Programs and Features for installed Adobe productsAffected if Neither Adobe Reader nor Adobe Acrobat is installed, then not affected
-
Determine the exact version numberNote the full version string displayed in the About dialog (for example: 10.1.15, 11.0.12, 15.006.30060, 15.008.20082)Affected if Version cannot be determined - manual inspection required
-
Compare Classic version to affected rangeFor Acrobat/Reader 10.x: check if version is 10.0 through 10.1.15. For 11.x: check if version is 11.0.0 through 11.0.12. For DC Classic: check if version is 15.006.30060 through 15.006.30093Affected if Version falls within any of these ranges - affected by CVE
-
Compare Continuous version to affected rangeFor DC Continuous track: check if version starts with 15.008.20082 through 15.009.20068Affected if Version falls within this range - affected by CVE
-
Confirm product type for DC versionsOn Windows, check the installation path: DC Continuous typically installs under Program Files/Adobe/Acrobat DC/ while DC Classic uses Program Files/Adobe/Acrobat 2015/Affected if Cannot distinguish - both DC tracks should be checked against their respective ranges
User is affected if Adobe Acrobat or Reader is installed AND the installed version matches any of the listed 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.
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 · scoped15.006.3009415.009.20069
Apply vendor patches: Adobe Reader/Acrobat 10.x to 10.1.16, 11.x to 11.0.13, DC Classic to 2015.006.30094, and DC Continuous to 2015.009.20069 or later.
Acrobat/Reader 10.1.16+, 11.0.13+, DC Classic 2015.006.30094+, or DC Continuous 2015.009.20069+
- 1. Check current Adobe Acrobat or Reader version by opening the application and navigating to Help > About Adobe Acrobat/Reader
- 2. Identify which product line and version you have (Acrobat/Reader, Classic/DC Continuous, version number)
- 3. For Acrobat/Reader 10.x: Upgrade to version 10.1.16 or later
- 4. For Acrobat/Reader 11.x: Upgrade to version 11.0.13 or later
- 5. For Acrobat/Reader DC Classic: Upgrade to version 2015.006.30094 or later
- 6. For Acrobat/Reader DC Continuous: Upgrade to version 2015.009.20069 or later
- 7. Download the appropriate updated version from the official Adobe website at https://get.adobe.com/reader/ or https://get.adobe.com/acrobat/
- 8. Close all Adobe applications before running the installer
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-6683 — 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-6683 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