dbcve.org
AcrobatApplication · Adobe

CVE-2015-4447

HIGH · 10.0 CVSS v2.0 Published 2015-07-15
Fix available
A fix is available. Upgrade to 10.1.15 / 11.0.12 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-4451, 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 · high confidence

This is a JavaScript API execution restriction bypass vulnerability in Adobe Reader and Acrobat. Attackers can exploit unspecified vectors to circumvent security controls that normally limit what JavaScript can do within PDF documents, potentially enabling arbitrary code execution or other malicious activities.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.15, 11.0.12, 2015.006.30060, or 2015.008.20082 or later. Until patched, consider disabling JavaScript in Adobe settings or deploying additional endpoint controls.

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
AcrobatApplication
Affected:>= 10.0, < 10.1.15>= 11.0.0, < 11.0.12
Acrobat DcApplication
Affected:>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082
Acrobat ReaderApplication
Affected:>= 10.0, < 10.1.15>= 11.0.0, < 11.0.12
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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Adobe product and version
    Open Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat (or Reader). Alternatively, right-click the application in Windows Task Manager and select Properties to view version information, or check Add/Remove Programs for the installed version number.
    Affected if The product is Adobe Acrobat or Reader (or Acrobat/Reader Dc) and the version falls within the affected ranges: 10.0 to 10.1.14, 11.0.0 to 11.0.11, 15.006.30033 to 15.006.30059, or 15.007.20033 to 15.008.20081.
  2. Confirm JavaScript is enabled in PDF settings
    In Adobe Acrobat/Reader, go to Edit > Preferences > JavaScript. Verify if 'Enable Adobe JavaScript' is checked. Also check Edit > Preferences > Security (Enhanced) for any JavaScript-related restrictions.
    Affected if JavaScript is enabled in the Adobe application settings (the vulnerability allows bypassing JavaScript restrictions, but requires JavaScript to be at least partially enabled to be exploitable).

You are affected if you have Adobe Acrobat or Reader installed with a version matching the affected ranges AND JavaScript processing is enabled in the application preferences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 10.1.15 / 11.0.12 / 15.006.30060 or later
Fixed in 10.1.1511.0.1215.006.30060
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Reader and Acrobat to version 10.1.15, 11.0.12, 2015.006.30060, or 2015.008.20082 or later. Until patched, consider disabling JavaScript in Adobe settings or deploying additional endpoint controls.

Recommended fix High confidence

Version 10.1.15, 11.0.12, 2015.006.30060 (DC Classic), or 2015.008.20082 (DC Continuous) depending on current product line

  1. Identify current Adobe Acrobat or Reader version via Help > About product
  2. For Acrobat/Reader 10.x: upgrade to version 10.1.15
  3. For Acrobat/Reader 11.x: upgrade to version 11.0.12
  4. For Acrobat/Reader DC Classic: upgrade to version 2015.006.30060
  5. For Acrobat/Reader DC Continuous: upgrade to version 2015.008.20082
  6. Download from official Adobe source: https://get.adobe.com/reader/ or https://get.adobe.com/acrobat/
  7. Install the updated version and restart the application
Caveat Standard upgrade risks apply (potential plugin/compatibility issues); prioritize security fix

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-4447 — 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-4447 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