CVE-2014-0496
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 · uneditedUse-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.9 and 11.x before 11.0.06 on Windows and Mac OS X allows attackers to execute arbitrary code via unspecified vectors.
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 confidenceUse-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.9 and 11.x before 11.0.06 allows attackers to execute arbitrary code via unspecified vectors. The vulnerability stems from memory being freed while pointers to it still exist, enabling controlled memory reuse for code execution.
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.1.9>= 11.0, < 11.0.6CVSS 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
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Check Adobe Acrobat version on WindowsOpen Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\Version (or 11.0\ProductVersion for 11.x branch), or right-click the AcroRd32.exe/Acrobat.exe file in Program Files, select Properties, and view the Version tabAffected if the ProductVersion value is 10.x less than 10.1.9, or 11.x less than 11.0.6
-
Check Adobe Acrobat version on Mac OS XOpen Finder, navigate to /Applications/Adobe Acrobat XI (or X), right-click the Adobe Acrobat app, select Get Info, and read the Version number under the General sectionAffected if the version displayed is 10.x less than 10.1.9, or 11.x less than 11.0.6
-
Check Adobe Reader version on WindowsOpen Windows Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Reader\Version (or 11.0\ProductVersion for 11.x branch), or right-click the AcroRd32.exe file in Program Files, select Properties, and view the Version tabAffected if the ProductVersion value is 10.x less than 10.1.9, or 11.x less than 11.0.6
-
Check Adobe Reader version on Mac OS XOpen Finder, navigate to /Applications/Adobe Reader XI (or X), right-click the Adobe Reader app, select Get Info, and read the Version numberAffected if the version displayed is 10.x less than 10.1.9, or 11.x less than 11.0.6
-
Verify exact version stringWithin the software, go to Help > About Adobe Acrobat (or Reader) to confirm the full version number including the minor release (for example, 10.1.8 or 11.0.5)Affected if the version shown is any release from 10.0 through 10.1.8, or 11.0 through 11.0.5
A system is affected if Adobe Acrobat or Adobe Reader version is 10.0 to 10.1.8 (10.x branch) or 11.0 to 11.0.5 (11.x branch) on Windows or Mac OS X, since the use-after-free flaw exists in the core application regardless of specific features enabled.
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 · scoped10.1.911.0.6
Update Adobe Reader and Acrobat to version 10.1.9 or 11.0.06 or later to remediate the vulnerability.
Adobe Acrobat 10.1.9 (for 10.x) or Adobe Acrobat 11.0.6 (for 11.x), or later versions
- Close all Adobe Reader and Acrobat applications before beginning the update
- Navigate to the official Adobe Acrobat support page (helpx.adobe.com) to download the latest version
- For Adobe Acrobat 10.x users: download and install version 10.1.9 or later
- For Adobe Acrobat 11.x users: download and install version 11.0.6 or later
- Alternatively, open Adobe Acrobat/Reader and go to Help > Check for Updates to receive the patched version automatically
- Follow the on-screen installation prompts to complete the update
- Restart your computer if prompted by the installer
- After installation, verify the version by opening Adobe Acrobat/Reader and navigating to Help > About Adobe Acrobat Reader to confirm the version number matches 10.1.9 or later for 10.x, or 11.0.6 or later for 11.x
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0496 — 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-0496 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