CVE-2014-0566
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 · uneditedAdobe 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-0565.
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 confidenceMemory 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 remote attackers to execute arbitrary code or cause denial of service via unspecified vectors.
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>= 10.0, < 10.1.15>= 11.0.0, < 11.0.12>= 10.0, < 10.1.15>= 11.0.0, < 11.0.12>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082>= 15.006.30033, < 15.006.30060>= 15.007.20033, < 15.008.20082CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Adobe Acrobat version via Windows RegistryOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\[Version] or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe Acrobat\[Version], then locate the 'Version' and 'Build' valuesAffected if The version is 10.x before 10.1.15, or 11.x before 11.0.12, or DC versions 15.006.30033 to 15.006.30059, or 15.007.20033 to 15.008.20081
-
Check Adobe Reader version via Windows RegistryOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Reader\[Version] or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe Reader\[Version], then locate the 'Version' and 'Build' valuesAffected if The version is 10.x before 10.1.15, or 11.x before 11.0.12, or DC versions 15.006.30033 to 15.006.30059, or 15.007.20033 to 15.008.20081
-
Check version from application executableLocate the Acrobat or Reader executable (e.g., AcroRd32.exe or AcroForm.exe in the program files directory), right-click and select Properties, then view the Details tab for version informationAffected if The version shown is within the affected ranges listed above
-
Check version via command lineOpen Command Prompt and run: dir "C:\Program Files\Adobe\Acrobat [Version]\*.*" /s | findstr "AcroRd32" or use wmic product get name,version for installed softwareAffected if The reported version falls within any of the affected version ranges
You are affected if any installed Adobe Acrobat or Adobe Reader version on Windows is below 10.1.15 (for 10.x), below 11.0.12 (for 11.x), or between 15.006.30033-15.006.30059, 15.007.20033-15.008.20081 (for DC classic or continuous track).
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.1.1511.0.1215.006.30060
Update Adobe Reader and Acrobat to version 10.1.12 or later (for 10.x) and 11.0.09 or later (for 11.x) to remediate this critical vulnerability.
Adobe Acrobat/Reader 10.1.15 or later; 11.0.12 or later; or for DC versions: 15.006.30060 or later / 15.008.20082 or later
- 1. Identify the currently installed Adobe Acrobat or Adobe Reader version by opening the application and navigating to Help > About (or About Adobe [Product])
- 2. Determine the product line (Traditional Acrobat/Reader vs. Acrobat Dc/Reader Dc) and the major version number (10.x, 11.x, or 15.x)
- 3. For Traditional Acrobat/Reader 10.x: Upgrade to version 10.1.15 or later
- 4. For Traditional Acrobat/Reader 11.x: Upgrade to version 11.0.12 or later
- 5. For Acrobat Dc/Reader Dc (version 15.006.x): Upgrade to version 15.006.30060 or later
- 6. For Acrobat Dc/Reader Dc (version 15.007.x and above): Upgrade to version 15.008.20082 or later
- 7. Download the appropriate updated version from the official Adobe website at https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 8. Close all Adobe applications before installing the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-0566 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2014-0566 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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