CVE-2013-0614
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 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1 allow attackers to execute arbitrary code via unspecified vectors, related to a "logic error," a different vulnerability than CVE-2013-0607, CVE-2013-0608, CVE-2013-0611, and CVE-2013-0618.
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 confidenceCVE-2013-0614 is a logic error vulnerability in Adobe Reader and Acrobat that allows remote attackers to execute arbitrary code on vulnerable systems. The vulnerability affects versions 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1. The specific exploitation vector is not detailed in the advisory, but the CVSS score of 10 indicates critical severity due to the code execution capability.
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= 9.0= 9.1= 9.1.1= 9.1.2= 9.1.3= 9.2= 9.3= 9.3.1= 9.3.2= 9.3.3= 9.3.4= 9.4= 9.0= 9.1= 9.1.1= 9.1.2= 9.1.3= 9.2= 9.3= 9.3.1= 9.3.2= 9.3.3= 9.3.4= 9.4CVSS 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 installed Adobe Acrobat versionOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Adobe\Adobe Acrobat\9.0\InstallProperties (adjust the 9.0 subkey for other major versions). Look for the "Version" or "ProductVersion" value in the right pane.Affected if The version value is 9.0 through 9.4, or the version starts with 9.x and is less than 9.5.3
-
Check installed Adobe Reader versionOpen Windows Registry Editor and navigate to HKLM\SOFTWARE\Adobe\Adobe Acrobat Reader\9.0\InstallProperties (adjust for other major versions). Check the "Version" value.Affected if The version is 9.0 through 9.4, or is any 9.x version below 9.5.3
-
Check Adobe Acrobat 10.x versionNavigate to HKLM\SOFTWARE\Adobe\Adobe Acrobat\10.0\InstallProperties in the registry and read the "Version" value.Affected if The version exists and is below 10.1.5
-
Check Adobe Reader 10.x versionNavigate to HKLM\SOFTWARE\Adobe\Adobe Acrobat Reader\10.0\InstallProperties in the registry and check the "Version" value.Affected if The version exists and is below 10.1.5
-
Check Adobe Acrobat 11.x versionNavigate to HKLM\SOFTWARE\Adobe\Adobe Acrobat\11.0\InstallProperties in the registry and examine the "Version" value.Affected if The version exists and is below 11.0.1
-
Alternative: Check via executable file propertiesRight-click AcroRd32.exe (Reader) or AcroDist.exe (Acrobat) in the installation directory, select Properties, and view the Details tab for the Product Version.Affected if The displayed version matches 9.0-9.4, any 10.x below 10.1.5, or any 11.x below 11.0.1
A system is affected if Adobe Acrobat or Adobe Reader is installed with version 9.x below 9.5.3, 10.x below 10.1.5, or 11.x below 11.0.1.
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 · scopedUpdate Adobe Reader and Acrobat to versions 9.5.3, 10.1.5, 11.0.1 or later to patch the vulnerability. Organizations should deploy the updates through their patch management infrastructure and verify successful installation across all affected systems.
Adobe Reader/Acrobat 9.5.3 or later (10.x users should go to 10.1.5+, 11.x users should go to 11.0.1+)
- Check the current Adobe Reader or Acrobat version by opening the application and navigating to Help > About Adobe Reader/Acrobat
- Download Adobe Reader 9.5.3 or later from the official Adobe website (get.adobe.com/reader) or Adobe Acrobat from get.adobe.com/acrobat
- Close all Adobe applications running on the system
- Run the downloaded installer and follow the prompts to update the software
- Restart the system after installation completes
- Verify the installed version by checking Help > About to confirm the update was successful
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0614 — 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-2013-0614 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