Acrobat ReaderApplication · Adobe

CVE-2014-0528

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
Double free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.10 and 11.x before 11.0.07 on Windows and 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 confidence

A double-free memory corruption vulnerability in Adobe Reader and Acrobat 10.x before 10.1.10 and 11.x before 11.0.07 on Windows and OS X allows attackers to execute arbitrary code via specially crafted PDF files or other unspecified vectors.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.10 or later (for 10.x) and 11.0.07 or later (for 11.x) to patch the vulnerability. In enterprise environments, test the update before broad deployment to ensure compatibility with existing PDF workflows.

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. Check if Adobe Reader is installed
    Open Windows Control Panel > Programs and Features, or run: wmic product where "name like 'Adobe Reader%'" get name,version
    Affected if Adobe Reader appears in the installed programs list
  2. Check if Adobe Acrobat is installed
    Open Windows Control Panel > Programs and Features, or run: wmic product where "name like 'Adobe Acrobat%'" get name,version
    Affected if Adobe Acrobat appears in the installed programs list
  3. Determine the exact version of Adobe Reader
    Right-click the Adobe Reader executable (typically in C:\Program Files\Adobe\Reader X\Reader\), select Properties, and view the Version tab. Or run: wmic product where "name like 'Adobe Reader%'" get version
    Affected if The version number is 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
  4. Determine the exact version of Adobe Acrobat
    Right-click the Adobe Acrobat executable (typically in C:\Program Files\Adobe\Acrobat X\Acrobat\), select Properties, and view the Version tab. Or run: wmic product where "name like 'Adobe Acrobat%'" get version
    Affected if The version number is 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

Your environment is affected if Adobe Reader or Adobe Acrobat version 10.0 through 10.1.7 is installed and you open untrusted PDF files.

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 later (for 10.x) and 11.0.07 or later (for 11.x) to patch the vulnerability. In enterprise environments, test the update before broad deployment to ensure compatibility with existing PDF workflows.

Recommended fix High confidence

Adobe Reader/Acrobat 10.1.10 or later (10.x line); 11.0.07 or later (11.x line) - upgrade to latest available version

  1. Identify the currently installed Adobe Reader or Acrobat version via Help > About Adobe Reader/Acrobat
  2. Download the fixed version from Adobe's official website (helpx.adobe.com) - for 10.x line use 10.1.10 or later, for 11.x line use 11.0.07 or later
  3. Close all Adobe Reader or Acrobat instances
  4. Install the updated version using Adobe's installer or update mechanism
  5. Restart the application and verify the version number reflects the patched release
Caveat Upgrading Adobe Acrobat may require accepting new license terms; ensure compatibility with existing PDF workflows before deploying

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

Fix this in Acrobat Reader Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0528 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