dbcve.org
Acrobat ReaderApplication · Adobe

CVE-2014-0522

HIGH · 10.0 CVSS v2.0 Published 2014-05-14
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.10 and 11.x before 11.0.07 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-0523, CVE-2014-0524, and CVE-2014-0526.

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

Adobe Reader and Acrobat 10.x before 10.1.10 and 11.x before 11.0.07 on Windows and OS X contain a memory corruption vulnerability allowing remote attackers to execute arbitrary code or cause a denial of service via unspecified vectors.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.10 or 11.0.07 or later to patch the memory corruption vulnerability.

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
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
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

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
    On Windows, check Programs and Features or the application Help > About. On OS X, check /Applications folder or the app's Info.plist.
    Affected if Adobe Reader or Adobe Acrobat is installed
  2. Determine Adobe Reader version
    On Windows, right-click AcroRd32.exe in the Reader installation folder (typically C:\Program Files\Adobe\Reader XX.X\Reader\) and select Properties > Details to view the version. On OS X, right-click Adobe Reader.app > Get Info.
    Affected if Version matches 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, or 10.1.7, or is 11.x before 11.0.07
  3. Determine Adobe Acrobat version
    On Windows, check the version of AcroPro.exe in the Acrobat installation folder (typically C:\Program Files\Adobe\Acrobat X.X\Acrobat\). On OS X, check Adobe Acrobat.app > Get Info.
    Affected if Version matches 10.0 through 10.1.7, or is 11.x before 11.0.07
  4. Confirm the product is running on Windows or OS X
    Verify the operating system. This vulnerability affects only Windows and OS X, not Linux.
    Affected if The operating system is Windows or OS X and the Adobe product version is in the affected range

A user is affected if Adobe Reader or Acrobat version 10.0-10.1.7 or 11.x before 11.0.07 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 version 10.1.10 or 11.0.07 or later to patch the memory corruption vulnerability.

Recommended fix High confidence

Adobe Reader/Acrobat 10.1.10 or higher (10.x line); Adobe Reader/Acrobat 11.0.07 or higher (11.x line)

  1. Identify the currently installed Adobe Reader or Acrobat version from the Help > About menu
  2. Download Adobe Reader 11.0.07 or later (or Adobe Acrobat 11.0.07 or later) from the official Adobe website
  3. Close all Adobe applications before running the installer
  4. Run the installer and follow the prompts to complete the upgrade
  5. Restart the computer after installation completes
  6. Verify the installed version matches or exceeds the fixed release (Help > About Adobe Reader/Acrobat)
Caveat Standard Adobe update - minimal risk; ensure backup of PDF files and preferences before upgrading in enterprise environments

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

Fix this in Acrobat Reader Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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