dbcve.org
AcrobatApplication · Adobe

CVE-2014-0524

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-0522, CVE-2014-0523, 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 · moderate 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 that allows 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 later for 10.x, and 11.0.07 or later for 11.x.

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
    Open Control Panel > Programs and Features (Windows) or inspect /Applications folder (macOS) for 'Adobe Reader'
    Affected if Adobe Reader appears in installed programs
  2. Check if Adobe Acrobat is installed
    Open Control Panel > Programs and Features (Windows) or inspect /Applications folder (macOS) for 'Adobe Acrobat'
    Affected if Adobe Acrobat appears in installed programs
  3. Locate Adobe Reader version
    Right-click Adobe Reader shortcut, select Properties, look at the Details tab for Product version, or open Adobe Reader and go to Help > About Adobe Reader
    Affected if Version starts with 10.x or 11.x and is earlier than 10.1.10 (for 10.x) or earlier than 11.0.07 (for 11.x)
  4. Locate Adobe Acrobat version
    Open Adobe Acrobat and go to Help > About Adobe Acrobat, or check the executable properties
    Affected if Version starts with 10.x or 11.x and is earlier than 10.1.10 (for 10.x) or earlier than 11.0.07 (for 11.x)
  5. Confirm exact version number
    Compare your installed version number against the affected list: 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 for 10.x
    Affected if Your installed version matches any of the listed affected versions

Your environment is affected if Adobe Reader or Adobe Acrobat version 10.x is before 10.1.10, or version 11.x is before 11.0.07.

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.

Recommended fix High confidence

Adobe Acrobat and Reader 10.1.10 (or migrate to latest 11.x which requires 11.0.07 or later)

  1. Navigate to helpx.adobe.com to download the latest Adobe Reader and Acrobat updates
  2. Download Adobe Acrobat and Reader version 10.1.10 or later for Windows and OS X
  3. Run the installer with administrator privileges
  4. Follow the on-screen prompts to complete the installation
  5. Restart the computer if prompted
  6. Verify the installed version by opening Adobe Reader/Acrobat and checking Help > About
Caveat Minor: Upgrading between major versions may reset some user preferences; ensure important settings are documented

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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