dbcve.org
AcrobatApplication · Adobe

CVE-2014-8447

HIGH · 10.0 CVSS v2.0 Published 2014-12-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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.13 and 11.x before 11.0.10 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-8445, CVE-2014-8446, CVE-2014-8456, CVE-2014-8458, CVE-2014-8459, CVE-2014-8461, and CVE-2014-9158.

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 confidence

Memory corruption vulnerability in Adobe Reader and Acrobat 10.x before 10.1.13 and 11.x before 11.0.10 on Windows and OS X allows attackers to execute arbitrary code or cause denial of service via unspecified vectors.

MitigationUpdate Adobe Reader and Acrobat to versions 10.1.13/11.0.10 or later. Consider disabling JavaScript in Adobe settings as a defense-in-depth measure.

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.0.1= 10.0.2= 10.0.3= 10.1= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7
Mac Os XOperating system
Affected:all versions
WindowsOperating system
Affected:all versions
Acrobat ReaderApplication
Affected:= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.1= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7

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. Verify Adobe product is installed
    Windows: Check registry key HKLM\SOFTWARE\Adobe\Adobe Acrobat or HKLM\SOFTWARE\Adobe\Adobe Reader in HKEY_LOCAL_MACHINE or HKEY_CURRENT_USER. Mac: Check /Applications for Adobe Acrobat or Adobe Reader.app
    Affected if Either Adobe Acrobat or Adobe Reader is present on the system
  2. Identify exact version number
    Windows: Read the Version value from the registry key found above. Mac: Right-click the app in Applications, select Get Info, and read the Version number
    Affected if Version starts with 10.0, 10.1 (through 10.1.7), or any 11.x version before 11.0.10
  3. Confirm product edition
    Windows: Check the registry for InstallLevel or the subkey name (Acrobat vs Reader). Mac: Verify if the app name contains 'Acrobat' (full product) or 'Reader'
    Affected if The installed product is Adobe Acrobat or Adobe Acrobat Reader matching the version range above
  4. Verify OS platform
    Confirm the system is running Windows or Apple Mac OS X
    Affected if The operating system is Windows or OS X (vulnerability affects only these platforms)

A user is affected if Adobe Acrobat or Adobe Reader version 10.0 through 10.1.7, or version 11.x before 11.0.10, is installed on Windows or OS X.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update Adobe Reader and Acrobat to versions 10.1.13/11.0.10 or later. Consider disabling JavaScript in Adobe settings as a defense-in-depth measure.

Recommended fix High confidence

Adobe Acrobat and Reader 10.1.13 (for 10.x versions) or 11.0.10 (for 11.x versions)

  1. 1. Close all Adobe Reader or Acrobat instances running on the system
  2. 2. Navigate to the Adobe Security Bulletins and Advisories page at helpx.adobe.com/security.html or access the direct download page
  3. 3. Locate the APSB14-24 security bulletin for CVE-2014-8447
  4. 4. Download the appropriate installer: For Adobe Acrobat 10.x, download version 10.1.13; For Adobe Acrobat 11.x, download version 11.0.10; For Adobe Reader 10.x, download version 10.1.13; For Adobe Reader 11.x, download version 11.0.10
  5. 5. Run the installer with administrator privileges
  6. 6. Follow the on-screen installation prompts
  7. 7. Restart the computer after installation completes
  8. 8. Verify the installed version by opening Adobe Reader/Acrobat and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to confirm the version number matches the expected fixed version

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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