dbcve.org
AcrobatApplication · Adobe

CVE-2015-4451

HIGH · 9.3 CVSS v2.0 Published 2015-07-15
Fix available
A fix is available. Upgrade to 15.006.30060 / 15.008.20082 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 · unedited
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 allow attackers to bypass JavaScript API execution restrictions via unspecified vectors, a different vulnerability than CVE-2015-4435, CVE-2015-4438, CVE-2015-4441, CVE-2015-4445, CVE-2015-4447, CVE-2015-4452, CVE-2015-5085, and CVE-2015-5086.

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

A detailed technical summary for this CVE is being prepared.

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
AcrobatApplication
Affected:>= 10.0, <= 10.1.14>= 11.0.0, <= 11.0.11
Acrobat DcApplication
Affected:>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082
Acrobat ReaderApplication
Affected:>= 10.0, <= 10.1.14>= 11.0.0, <= 11.0.11
Acrobat Reader DcApplication
Affected:>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082

CVSS 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
M
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:M/Au:N/C:C/I:C/A:C

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 · scoped
Upgrade available Upgrade to 15.006.30060 / 15.008.20082 or later
Fixed in 15.006.3006015.008.20082
Vendor patch helpx.adobe.com →
Recommended fix High confidence

Adobe Acrobat/Reader 10.1.15, 11.0.12, DC Classic 2015.006.30060, or DC Continuous 2015.008.20082 or later

  1. 1. Identify the exact Adobe product (Acrobat or Acrobat Reader) and version currently installed. In Adobe Acrobat/Reader, go to Help > About Adobe Acrobat Reader/Adobe Acrobat to confirm the version number.
  2. 2. For Acrobat/Acrobat Reader 10.x (versions 10.0 through 10.1.14): Upgrade to version 10.1.15 or later.
  3. 3. For Acrobat/Acrobat Reader 11.x (versions 11.0.0 through 11.0.11): Upgrade to version 11.0.12 or later.
  4. 4. For Acrobat/Acrobat Reader DC Classic (versions 15.006.30033 through 15.006.30059): Upgrade to version 15.006.30060 or later.
  5. 5. For Acrobat/Acrobat Reader DC Classic (versions 15.007.20033 through 15.008.20081): Upgrade to version 15.008.20082 or later.
  6. 6. For Acrobat/Acrobat Reader DC Continuous: Ensure the automatic update feature is enabled or manually download the latest version from the Adobe website.
  7. 7. Verify the installation of the patched version by checking Help > About again.
Caveat Standard upgrade considerations apply - verify compatibility with existing workflows and ensure no custom JavaScript scripts rely on the vulnerable behavior

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4451 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-4451 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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