dbcve.org
AcrobatApplication · Adobe

CVE-2014-0565

HIGH · 10.0 CVSS v2.0 Published 2014-09-17
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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.12 and 11.x before 11.0.09 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-0566.

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.12 and 11.x before 11.0.09 on Windows and OS X allows arbitrary code execution or denial of service via unspecified vectors.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.12, 11.0.09, or later to remediate this 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
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. Identify if Adobe Reader or Adobe Acrobat is installed
    Windows: Open Programs and Features or check Registry under HKLM\SOFTWARE\Adobe\ for Adobe Acrobat or Adobe Reader keys. macOS: Check /Applications for Adobe Acrobat or Adobe Reader folders.
    Affected if Either Adobe Reader or Adobe Acrobat is present on the system
  2. Determine the exact version number of the installed Adobe product
    Windows: Right-click the executable (AcroRd32.exe or AcroTray.exe) in the install directory, select Properties, and view the Version tab. Alternatively, run reg query for the version key. macOS: Right-click the Adobe app in /Applications, select Get Info, and view the Version field.
    Affected if The installed version cannot be determined or does not match expected Adobe versioning
  3. Compare the installed version against affected ranges
    Check if the version is 10.0 through 10.1.7 (any 10.x before 10.1.12) or 11.0 through 11.0.08 (any 11.x before 11.0.09).
    Affected if Version 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, or any 11.x version before 11.0.09

The system is vulnerable if Adobe Reader or Adobe Acrobat version 10.0 through 10.1.7 or 11.0 through 11.0.08 is installed on Windows or macOS.

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
Patch available Apply the vendor patch
Vendor patch helpx.adobe.com →
Interim mitigation

Update Adobe Reader and Acrobat to version 10.1.12, 11.0.09, or later to remediate this vulnerability.

Recommended fix High confidence

Adobe Reader/Acrobat 10.1.12 or later for 10.x users; Adobe Reader/Acrobat 11.0.09 or later for 11.x users

  1. Identify the installed Adobe Reader or Acrobat version (Help > About in the application)
  2. For Adobe 10.x versions: Upgrade to version 10.1.12 or later
  3. For Adobe 11.x versions: Upgrade to version 11.0.09 or later
  4. Download the latest version from the official Adobe download page at adobe.com or from the vendor security bulletin at helpx.adobe.com/security/products/reader/apsb14-20.html
  5. Install the updated version and restart the application
  6. Verify the version has been updated successfully
Caveat Adobe 10.x is end-of-life and no longer receives security updates; consider migrating to a supported version (11.x or later)

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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