CVE-2015-3075
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-3059.
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. The vulnerability stems from improper memory management where the software continues using a pointer after the associated memory has been freed, potentially enabling remote 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.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.
-
Verify Adobe Acrobat or Reader is installedOn Windows, check Start Menu for Adobe Acrobat/Reader or go to Control Panel > Programs and Features. On macOS, check /Applications folder for Adobe Acrobat or Adobe Reader.Affected if Adobe Acrobat or Adobe Reader is present on the system
-
Determine the installed version on WindowsRight-click the Adobe Acrobat/Reader shortcut, select Properties, and check the Details tab for the product version. Alternatively, open the application, go to Help > About Adobe Acrobat/Reader to view the exact version number.Affected if The version shown is 10.x (any version before 10.1.14) or 11.x (any version before 11.0.11)
-
Determine the installed version on macOSOpen Finder, navigate to /Applications, right-click Adobe Acrobat/Reader, select Get Info, and check the Version field under General information.Affected if The version shown is 10.x (any version before 10.1.14) or 11.x (any version before 11.0.11)
-
Confirm the operating system is affectedVerify the system is running Windows (any version) or Apple macOS (any version) as listed in the affected products.Affected if The system runs Windows or macOS, and the Adobe product version is within the vulnerable range
A user is affected if Adobe Acrobat or Adobe Reader version 10.1.0 through 10.1.13 (for the 10.x line) or version 11.0.0 through 11.0.10 (for the 11.x line) is installed on Windows or macOS.
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 the 10.x line, and 11.0.11 or later for the 11.x line. Prioritize patching systems with direct internet exposure or those processing untrusted PDF documents.
Adobe Reader/Acrobat 10.1.14 (for 10.x versions) or 11.0.11 (for 11.x versions)
- Close all Adobe Reader and Acrobat instances before installing the update
- Navigate to the Adobe security bulletin APSB15-10 at https://helpx.adobe.com/security/products/reader/apsb15-10.html
- Download the appropriate patch for your platform (Windows or Mac OS X) and product version
- For Adobe Reader/Acrobat 10.x, download and install update version 10.1.14
- For Adobe Reader/Acrobat 11.x, download and install update version 11.0.11
- Run the installer and follow the on-screen prompts to complete the update
- After installation, launch Adobe Reader/Acrobat and verify the version by checking Help > About (Windows) or Adobe Reader/Acrobat > About Adobe Reader/Acrobat (Mac)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3075 — 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-3075 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