CVE-2015-3051
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-3046, CVE-2015-3049, CVE-2015-3050, 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 attackers to execute arbitrary code or cause denial of service. This is a critical client-side vulnerability distinct from other related CVEs in the same period.
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 if Adobe Reader or Acrobat is installedWindows: Check Program Files for Adobe folders, or open Registry Editor and look under HKEY_LOCAL_MACHINE\SOFTWARE\Adobe. Mac: Check /Applications for Adobe Acrobat or Adobe Reader.Affected if Either Adobe Reader or Adobe Acrobat is present on the system
-
Determine installed Adobe product version on WindowsOpen Adobe Reader or Acrobat, then go to Help > About Adobe Reader/Acrobat. Alternatively, in Windows Explorer right-click the executable (e.g., AcroRd32.exe in Program Files\Adobe\Reader 10.0\Reader) and view Properties > Details for the Product Version.Affected if Version matches 10.1.0 through 10.1.13 for 10.x line, or is 11.x version lower than 11.0.11
-
Determine installed Adobe product version on Mac OS XOpen Adobe Reader or Acrobat, then go to Adobe Reader/Acrobat > About Adobe Reader/Acrobat. Alternatively, in Finder navigate to /Applications/Adobe Reader 10.x or Adobe Acrobat 10.x, right-click the app, select Get Info, and view the Version field.Affected if Version matches 10.1.0 through 10.1.13 for 10.x line, or is 11.x version lower than 11.0.11
-
Check Windows registry for exact versionOpen Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Reader\10.0\InstallPath (adjust version number as needed), check the value of Version key. Do the same for Acrobat under HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\10.0 (or 11.0).Affected if Version key value is 10.1.0 through 10.1.13 for 10.x, or 11.0.0 through 11.0.10 for 11.x
A user is affected if Adobe Reader or Adobe Acrobat version 10.1.0 through 10.1.13 (10.x line) or version 11.0.0 through 11.0.10 (11.x line) is installed on Windows or Mac OS X.
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 remediate this vulnerability.
Adobe Reader/Acrobat 10.1.14 (for 10.x) or 11.0.11 (for 11.x)
- 1. Verify the currently installed Adobe Reader or Acrobat version by opening the application, selecting Help > About Adobe Reader (or About Adobe Acrobat).
- 2. If running version 10.x (10.1.0 through 10.1.13), download and install Adobe Acrobat and Reader 10.1.14 from the Adobe security bulletin APSB15-10.
- 3. If running version 11.x (11.0.0 through 11.0.10), download and install Adobe Acrobat and Reader 11.0.11 from the Adobe security bulletin APSB15-10.
- 4. Ensure the installed version matches the target fixed version (10.1.14 or 11.0.11) by checking Help > About again.
- 5. Apply any subsequent security updates as they become available.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-3051 — 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-3051 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