CVE-2015-3059
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.14 and 11.x before 11.0.11 on Windows and OS X allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-3053, CVE-2015-3054, CVE-2015-3055, and CVE-2015-3075.
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 confidenceA use-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.14 and 11.x before 11.0.11 on Windows and OS X allows attackers to execute arbitrary code via unspecified vectors through improper memory management.
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.1.0= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7= 10.1.8= 10.1.9= 10.1.10= 10.1.11all versionsall versions= 10.1.0= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7= 10.1.8= 10.1.9= 10.1.10= 10.1.11CVSS 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 productOn Windows: Open Control Panel > Programs and Features, or check registry key HKLM\Software\Adobe\Acrobat\Install. On Mac: Open Finder > Applications, right-click Adobe app > Get Info, or run 'system_profiler SPApplicationsDataType' in Terminal.Affected if Adobe Reader or Acrobat is installed on the system
-
Determine exact version numberFor Windows: In Programs and Features, find Adobe Reader or Acrobat and note the version in the column. For Adobe Acrobat, you can also open the application, go to Help > About Adobe Acrobat. For Mac: Check the version shown in the Get Info window.Affected if Version shows 10.1.x where x is 0-11, or 11.0.x where x is 0-10 (any version before 10.1.14 for 10.x or before 11.0.11 for 11.x)
-
Confirm product is Adobe Reader or AcrobatVerify the product name in Programs and Features (Windows) or Applications folder (Mac) is either 'Adobe Reader' or 'Adobe Acrobat' (Standard, Pro, or XI).Affected if Product is Adobe Reader or Adobe Acrobat version 10.x or 11.x within the affected ranges
If Adobe Reader or Acrobat version is 10.1.0 through 10.1.11, or 11.0.0 through 11.0.10 on Windows or Mac OS X, the system is vulnerable to CVE-2015-3059.
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 · scopedUpdate Adobe Reader and Acrobat to version 10.1.14 or later (for 10.x) or 11.0.11 or later (for 11.x) to patch the vulnerability.
Acrobat/Acrobat Reader 10.1.14 or 11.0.11 (depending on your major version)
- Visit the Adobe security bulletin at https://helpx.adobe.com/security/products/reader/apsb15-10.html to download the fixed version
- Identify your currently installed Adobe Acrobat or Adobe Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat)
- For Acrobat/Acrobat Reader 10.x users: Download and install version 10.1.14
- For Acrobat/Acrobat Reader 11.x users: Download and install version 11.0.11
- Alternatively, use the automatic update feature: Open Adobe Reader/Acrobat, go to Help > Check for Updates, and follow the prompts to install the security update
- Verify the installation was successful by checking the version number again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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 $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3059 — 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-3059 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