CVE-2015-5108
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 · uneditedInteger overflow in 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 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-5097 and CVE-2015-5109.
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 confidenceInteger overflow vulnerability in Adobe Reader and Acrobat allows attackers to execute arbitrary code via unspecified vectors. The overflow occurs in the arithmetic handling within the software, where insufficient bounds checking can cause memory corruption that may be leveraged for 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.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082>= 10.0, < 10.1.15>= 11.0.0, < 11.0.12>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082CVSS 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 productOpen Adobe Reader or Acrobat, go to Help > About Adobe [Product], or right-click the application executable and select Properties > Details to view the version numberAffected if The product is Adobe Reader or Adobe Acrobat (including DC variants)
-
Determine exact version numberNote the full version string displayed (for example, 10.1.12 or 15.006.30033)Affected if A version is displayed showing the installed release
-
Check if version is in affected range for 10.x/11.xCompare your version to: 10.0 to 10.1.14 (10.x), or 11.0.0 to 11.0.11 (11.x). Any version >= 10.0 but < 10.1.15, or >= 11.0.0 but < 11.0.12 is vulnerable.Affected if Installed version falls within 10.0 <= version < 10.1.15 OR 11.0.0 <= version < 11.0.12
-
Check if version is in affected range for DC ClassicCompare your version to the DC Classic range: version >= 15.006.30033 but < 15.006.30060Affected if Installed DC Classic version is 15.006.30033 through 15.006.30059
-
Check if version is in affected range for DC ContinuousCompare your version to the DC Continuous range: version >= 15.007.20033 but < 15.008.20082Affected if Installed DC Continuous version is 15.007.20033 through 15.008.20081
You are affected if the installed Adobe Reader or Acrobat version matches any of the four vulnerable ranges: 10.x (< 10.1.15), 11.x (< 11.0.12), DC Classic (< 15.006.30060), or DC Continuous (< 15.008.20082).
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 · scoped10.1.1511.0.1215.006.30060
Apply the vendor patches: update Adobe Reader/Acrobat 10.x to 10.1.15 or later, 11.x to 11.0.12 or later, DC Classic to 2015.006.30060 or later, and DC Continuous to 2015.008.20082 or later.
10.1.15 (10.x), 11.0.12 (11.x), 2015.006.30060 (DC Classic), 2015.008.20082 (DC Continuous)
- 1. Identify the currently installed Adobe Acrobat or Reader version by navigating to Help > About (or using the built-in version checker)
- 2. Based on the installed product line, download the appropriate fixed version from Adobe's official security advisory page at https://helpx.adobe.com/security/products/reader/apsb15-15.html
- 3. For Acrobat/Reader 10.x, upgrade to version 10.1.15 or later
- 4. For Acrobat/Reader 11.x, upgrade to version 11.0.12 or later
- 5. For Acrobat/Reader DC Classic, upgrade to version 2015.006.30060 or later
- 6. For Acrobat/Reader DC Continuous, upgrade to version 2015.008.20082 or later
- 7. Apply the update using standard Adobe installation procedures (or enterprise deployment tools if applicable)
- 8. Verify the update was successful by checking the version number post-installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-5108 — 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-5108 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