CVE-2015-7650
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 · uneditedAdobe 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 allow attackers to execute arbitrary code or cause a denial of service (out-of-bounds read and memory corruption) via a crafted CMAP table in a PDF document, a different vulnerability than CVE-2015-6685, CVE-2015-6686, CVE-2015-6693, CVE-2015-6694, CVE-2015-6695, and CVE-2015-7622.
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 confidenceOut-of-bounds read vulnerability in Adobe Reader, Acrobat, and Acrobat Reader DC when parsing a crafted CMAP table in PDF documents. This allows remote attackers to execute arbitrary code or cause denial of service via memory corruption.
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
- M
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:M/Au:N/C:P/I:P/A:P
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 the installed Adobe productOpen Adobe Reader or Acrobat and navigate to Help > About Adobe [Product Name] to see the exact product name and version numberAffected if The product is Adobe Acrobat, Acrobat DC, Acrobat Reader, or Acrobat Reader DC and the version falls within the affected ranges
-
Determine the exact version numberNote the full version number displayed in the About dialog (for example: 10.1.15, 11.0.12, 15.006.30060, or 15.008.20082)Affected if The installed version matches one of the affected version ranges listed in the CVE details
-
Compare version against affected rangesFor Acrobat/Reader 10.x: version must be 10.0 through 10.1.15. For 11.x: version must be 11.0.0 through 11.0.12. For DC (Continuous): version 15.006.30060 through 15.006.30093 or 15.008.20082 through 15.009.20068Affected if The installed version is within any of these 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
-
Confirm CMAP parsing is possibleThis vulnerability is triggered when parsing a crafted CMAP table inside a PDF file. The attack requires opening a malicious PDF document that contains a specially crafted CMAP tableAffected if The vulnerable version is installed AND the user opens untrusted PDF files that could contain a crafted CMAP table
The user is affected if they have Adobe Acrobat, Acrobat DC, Acrobat Reader, or Acrobat Reader DC installed with a version number within the 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.
From vendor data15.006.3009415.009.20069
Update Adobe products to version 10.1.16 or later for 10.x, 11.0.13 or later for 11.x, or the specified Continuous/Classic patches for DC versions. Avoid opening untrusted PDF files as a defense-in-depth measure.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-7650 — 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-7650 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