CVE-2015-3046
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.14 and 11.x before 11.0.11 on Windows and OS X allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2014-9161, CVE-2015-3049, CVE-2015-3050, CVE-2015-3051, CVE-2015-3052, CVE-2015-3056, CVE-2015-3057, CVE-2015-3070, and CVE-2015-3076.
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 · moderate confidenceMemory corruption 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 remote attackers to execute arbitrary code or cause denial of service via unspecified vectors.
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 PDF softwareOpen Windows Control Panel > Programs and Features, or on macOS open Finder > Applications and look for Adobe Acrobat or Adobe Reader entriesAffected if Neither Adobe Acrobat nor Adobe Reader is installed, then not affected
-
Determine Adobe Acrobat versionIf Adobe Acrobat is installed, open it, then go to Help > About Adobe Acrobat to view the exact version number (format: xx.x.xxxxx)Affected if Version shows 10.1.x where x is 0-11, or version shows 11.0.x where x is 0-10, then affected
-
Determine Adobe Reader versionIf Adobe Reader is installed, open it, then go to Help > About Adobe Reader to view the exact version number (format: xx.x.xxxxx)Affected if Version shows 10.1.x where x is 0-11, or version shows 11.0.x where x is 0-10, then affected
-
Verify exact build number on WindowsRight-click the Adobe application in Programs and Features, select Properties, and check the Details tab for the Product Version fieldAffected if Build number falls within 10.1.0 through 10.1.11 or 11.0.0 through 11.0.10, then affected
Your environment is affected if Adobe Acrobat or Adobe Reader version 10.1.0 through 10.1.11 or version 11.0.0 through 11.0.10 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 11.0.11 or later to remediate this vulnerability.
Acrobat/Reader 10.x to 10.1.14; Acrobat/Reader 11.x to 11.0.11
- 1. Identify the currently installed Adobe Acrobat or Adobe Reader version by navigating to Help > About (or pressing Ctrl+Shift+I in Reader)
- 2. Determine whether you have version 10.x or 11.x installed
- 3. For Acrobat/Reader 10.x users: Download version 10.1.14 from the Adobe website or your organization's software distribution point
- 4. For Acrobat/Reader 11.x users: Download version 11.0.11 from the Adobe website or your organization's software distribution point
- 5. Close all Adobe Acrobat/Reader instances and any applications with PDF integration
- 6. Run the downloaded installer with appropriate administrator privileges
- 7. Restart the system after installation completes
- 8. Verify the installed version matches the target (10.1.14 or 11.0.11) by checking About dialog
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3046 — 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-3046 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