dbcve.org
AcrobatApplication · Adobe

CVE-2014-0495

HIGH · 10.0 CVSS v2.0 Published 2014-01-15
Fix available
A fix is available. Upgrade to 10.1.9 / 11.0.6 or later.
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.9 and 11.x before 11.0.06 on Windows and Mac 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-0493.

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

Memory corruption 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 remote attackers to execute arbitrary code or cause denial of service via unspecified vectors. The CVSS 10 score indicates critical severity, likely indicating active exploitation or easily exploitable conditions.

MitigationUpgrade Adobe Reader and Acrobat to version 10.1.9 or later (for 10.x) and 11.0.06 or later (for 11.x) on all affected Windows and Mac systems. Consider disabling Adobe Reader/Acrobat until patches can be applied if immediate risk is unacceptable.

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.9>= 11.0, < 11.0.6

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 Reader or Acrobat version
    On Windows, open the application and go to Help > About Adobe Acrobat Reader (or Acrobat). Alternatively, right-click the executable file (e.g., AcroRd32.exe or AcroDist.exe in the installation folder) and select Properties > Details to view the Product Version.
    Affected if The displayed version falls within 10.0.0 through 10.1.8.x OR 11.0.0 through 11.0.5.x.
  2. Confirm product type
    Verify whether the installed product is Adobe Reader or Adobe Acrobat. The vulnerability affects both product lines.
    Affected if The product is Adobe Reader or Adobe Acrobat versions 10.x or 11.x.
  3. Check operating system platform
    Verify the system is running Windows or Mac OS X, as these are the only affected platforms listed for this CVE.
    Affected if The operating system is Windows or Mac OS X.
  4. Review software inventory or deployment records
    If managing multiple systems, use software inventory or endpoint management tools to scan for Adobe Reader or Acrobat installations and capture their exact version numbers across the environment.
    Affected if Any discovered installation matches the affected version ranges.

A system is affected if Adobe Reader or Acrobat version 10.x (before 10.1.9) or 11.x (before 11.0.6) is installed on Windows or Mac 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
Upgrade available Upgrade to 10.1.9 / 11.0.6 or later
Fixed in 10.1.911.0.6
Interim mitigation

Upgrade Adobe Reader and Acrobat to version 10.1.9 or later (for 10.x) and 11.0.06 or later (for 11.x) on all affected Windows and Mac systems. Consider disabling Adobe Reader/Acrobat until patches can be applied if immediate risk is unacceptable.

Recommended fix High confidence

Acrobat/Reader 10.1.9 (for 10.x) or 11.0.6 (for 11.x), preferably latest available version

  1. 1. Open Adobe Acrobat or Adobe Reader on your system
  2. 2. Navigate to Help > About Adobe Acrobat (or About Adobe Reader) to check the current version
  3. 3. If running version 10.x and below 10.1.9, or version 11.x and below 11.0.6, an upgrade is required
  4. 4. Download the latest version of Adobe Acrobat or Adobe Reader from the official Adobe website (get.adobe.com/reader for Reader, or adobe.com for Acrobat)
  5. 5. Run the installer and follow the prompts to complete the upgrade
  6. 6. Restart any running Adobe applications after the upgrade completes
  7. 7. Verify the installed version shows 10.1.9 or higher for 10.x, or 11.0.6 or higher for 11.x
Caveat Standard security updates typically have no breaking changes; however, some legacy features or plugins may behave differently in newer major versions

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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 locally
dbcve dependency scanner

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