dbcve.org
AcrobatApplication · Adobe

CVE-2014-0527

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

Use-after-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. The flaw occurs when memory is deallocated but the program continues to use a dangling pointer, potentially allowing controlled memory corruption and remote code execution.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.10 or later (for 10.x) and 11.0.07 or later (for 11.x) on Windows and OS X systems.

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

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
    On Windows, open Add/Remove Programs (Programs and Features) and look for 'Adobe Reader' in the installed programs list, or check for the existence of C:\Program Files\Adobe\Reader XX.X\Reader\AcroRd32.exe
    Affected if Adobe Reader version 10.0 through 10.1.7 or 11.0 through 11.0.06 is present
  2. Check if Adobe Acrobat is installed
    On Windows, open Add/Remove Programs (Programs and Features) and look for 'Adobe Acrobat' in the installed programs list, or check for the existence of C:\Program Files\Adobe\Acrobat XX.X\Acrobat\Acrobat.exe
    Affected if Adobe Acrobat version 10.0 through 10.1.7 or 11.0 through 11.0.06 is present
  3. Determine the installed Adobe Reader version
    Right-click on AcroRd32.exe in the Adobe Reader installation folder, select Properties, and view the Version tab. Alternatively, run 'wmic product where "name like 'Adobe Reader%'" get version, name' in Command Prompt
    Affected if The version shown 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, 10.1.7, 11.0, 11.0.01, 11.0.02, 11.0.03, 11.0.04, 11.0.05, or 11.0.06
  4. Determine the installed Adobe Acrobat version
    Right-click on Acrobat.exe in the Adobe Acrobat installation folder, select Properties, and view the Version tab. Alternatively, run 'wmic product where "name like 'Adobe Acrobat%'" get version, name' in Command Prompt
    Affected if The version shown 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, 10.1.7, 11.0, 11.0.01, 11.0.02, 11.0.03, 11.0.04, 11.0.05, or 11.0.06

You are affected if Adobe Reader or Adobe Acrobat version 10.0 through 10.1.7 or 11.0 through 11.0.06 is installed on your Windows or OS X system.

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) on Windows and OS X systems.

Recommended fix High confidence

Acrobat/Reader 10.1.10 or later (or 11.0.07+ for 11.x users)

  1. 1. Close Adobe Acrobat or Adobe Reader if currently open
  2. 2. Navigate to the Adobe Acrobat download page or use Adobe's Creative Cloud/Update mechanism
  3. 3. Download Adobe Acrobat or Reader version 10.1.10 or later for the 10.x product line
  4. 4. Run the installer and follow the on-screen prompts
  5. 5. After installation, restart any Adobe applications and verify the version via Help > About Adobe Acrobat Reader
Caveat Standard upgrade; ensure compatibility with existing PDF workflows and plugins before deploying in production

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

Fix this in Acrobat 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-0527 — 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-0527 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