dbcve.org
AcrobatApplication · Adobe

CVE-2013-0606

HIGH · 10.0 CVSS v2.0 Published 2013-01-10
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
Buffer overflow in Adobe Reader and Acrobat 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2013-0612, CVE-2013-0615, CVE-2013-0617, and CVE-2013-0621.

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

Buffer overflow vulnerability in Adobe Reader and Acrobat affecting versions 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1. The flaw allows remote attackers to execute arbitrary code via unspecified vectors, likely through malicious PDF files.

MitigationUpdate Adobe Reader and Acrobat to version 9.5.3, 10.1.5, or 11.0.1 or later to remediate the vulnerability. Apply through Adobe's official channels.

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:= 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
Acrobat ReaderApplication
Affected:= 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

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 Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Reader or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe Reader. On Mac, check /Applications/ for Adobe Reader.app.
    Affected if The registry key or application folder exists, indicating Adobe Reader is present
  2. Determine the installed Adobe Reader version
    In Windows Registry, look at the "Version" or "InstanceVersion" value under the Adobe Reader key. On Mac, right-click Adobe Reader.app, select Get Info, and read the Version field.
    Affected if The version starts with 9.0 through 9.4, or 10.0 through 10.1.4, or 11.0.0 (any version before the fixed releases)
  3. Check if Adobe Acrobat is installed
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat or HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Adobe\Adobe Acrobat. On Mac, check /Applications/ for Adobe Acrobat.app.
    Affected if The registry key or application folder exists, indicating Adobe Acrobat is present
  4. Determine the installed Adobe Acrobat version
    In Windows Registry, examine the "Version" or "InstanceVersion" value under the Adobe Acrobat key. On Mac, right-click Adobe Acrobat.app, select Get Info, and read the Version field.
    Affected if The version is 9.0 through 9.4 (the listed affected versions for Acrobat)

You are affected if Adobe Reader or Adobe Acrobat is installed and the version falls within 9.0-9.4, 10.0-10.1.4, or 11.0.0.

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 9.5.3, 10.1.5, or 11.0.1 or later to remediate the vulnerability. Apply through Adobe's official channels.

Recommended fix High confidence

Adobe Reader/Acrobat 9.5.3 or later (10.1.5 for 10.x, 11.0.1 for 11.x)

  1. 1. Close Adobe Reader or Acrobat if currently running
  2. 2. Download Adobe Reader/Acrobat version 9.5.3 or later from the official Adobe website (https://get.adobe.com/reader/)
  3. 3. Run the installer with administrative privileges
  4. 4. Follow the on-screen installation prompts
  5. 5. Restart the computer after installation completes
  6. 6. Verify the installed version by opening Adobe Reader, going to Help > About Adobe Reader
Caveat Minor: Some legacy features or plugins may need reconfiguration after upgrade

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
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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