CVE-2014-8451
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 · uneditedAn unspecified JavaScript API 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 obtain sensitive information via unknown vectors, a different vulnerability than CVE-2014-8448.
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 confidenceAn information disclosure vulnerability in an unspecified JavaScript API 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 obtain sensitive information via unknown 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.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.7all versionsall versions= 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.7CVSS 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
- Partial
- Integrity
- None
- Availability
- None
AV:N/AC:L/Au:N/C:P/I:N/A:N
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 Acrobat or Reader is installedCheck installed programs list in Windows Control Panel > Programs and Features, or on macOS check /Applications folder for Adobe Acrobat or Adobe ReaderAffected if Either Adobe Acrobat or Adobe Reader is present on the system
-
Determine the installed Adobe product versionOpen the application, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to view the exact version number, or check the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat\InstallInfo or on macOS check the app bundle Info.plistAffected if The displayed version matches 10.0.x or 10.1.x through 10.1.7, or any 11.x version before 11.0.10
-
Confirm the product edition and update versionCompare your exact version (such as 10.1.7, 10.0.4, 11.0.9, etc.) against the fixed releases 10.1.13 and 11.0.10Affected if The installed version is lower than 10.1.13 for the 10.x line or lower than 11.0.10 for the 11.x line, or is exactly one of the listed affected versions (10.0 through 10.1.7)
A user is affected if Adobe Acrobat or Adobe Reader version 10.0 through 10.1.7, or 11.x before 11.0.10, is installed on Windows or 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.
From vendor dataUpdate Adobe Reader and Acrobat to versions 10.1.13 or 11.0.10 or later to remediate this vulnerability.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-8451 — 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-2014-8451 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