dbcve.org
AcrobatApplication · Adobe

CVE-2013-0609

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
Integer 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-0613.

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

Integer overflow vulnerability in Adobe Reader and Acrobat versions 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1 allows remote attackers to execute arbitrary code via unspecified vectors. This is distinct from the related CVE-2013-0613.

MitigationUpdate Adobe Reader and Acrobat to version 9.5.3, 10.1.5, 11.0.1 or later to patch the integer overflow 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:= 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 Adobe Reader version
    Open Adobe Reader, then go to Help > About Adobe Reader to display the version number
    Affected if Version starts with 9.x and is earlier than 9.5.3, or starts with 10.x and is earlier than 10.1.5, or starts with 11.x and is earlier than 11.0.1
  2. Check Adobe Acrobat version
    Open Adobe Acrobat, then go to Help > About Adobe Acrobat to display the version number
    Affected if Version starts with 9.x and is earlier than 9.5.3, or starts with 10.x and is earlier than 10.1.5, or starts with 11.x and is earlier than 11.0.1
  3. Check installed version via Windows Programs and Features
    Open Control Panel > Programs and Features (or Settings > Apps on Windows 10/11), locate Adobe Acrobat Reader or Adobe Acrobat in the list and note the version column
    Affected if The listed version falls within the affected ranges: 9.0 through 9.4, or any 10.x version before 10.1.5, or any 11.x version before 11.0.1
  4. Check executable file version directly
    Locate the Adobe executable (e.g., AcroRd32.exe for Reader or AcroRd32.exe for Acrobat, typically in C:\Program Files\Adobe\Adobe Reader X\Reader\ or similar path), right-click the file, select Properties, and check the Details tab for Product Version
    Affected if The file version shows a version matching the affected ranges: 9.0.x through 9.4.x, 10.x before 10.1.5, or 11.x before 11.0.1

If Adobe Reader or Adobe Acrobat is installed with any version from 9.0 through 9.4, any 10.x before 10.1.5, or any 11.x before 11.0.1, the environment is affected by this integer overflow vulnerability.

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, 11.0.1 or later to patch the integer overflow vulnerability.

Recommended fix High confidence

Adobe Acrobat/Reader 9.5.3+, 10.1.5+, or 11.0.1+ (choose the major version branch relevant to your environment)

  1. Identify the currently installed Adobe Acrobat or Adobe Reader version from the Help > About menu
  2. For Adobe Acrobat 9.x users: Upgrade to Adobe Acrobat 9.5.3 or later
  3. For Adobe Acrobat 10.x users: Upgrade to Adobe Acrobat 10.1.5 or later
  4. For Adobe Acrobat 11.x users: Upgrade to Adobe Acrobat 11.0.1 or later
  5. For Adobe Reader 9.x users: Upgrade to Adobe Reader 9.5.3 or later
  6. For Adobe Reader 10.x users: Upgrade to Adobe Reader 10.1.5 or later
  7. For Adobe Reader 11.x users: Upgrade to Adobe Reader 11.0.1 or later
  8. Verify the version after installation from Help > About to confirm the fix is applied
Caveat Newer versions may have compatibility issues with older PDF forms, scripts, or third-party plugins; test in non-production environment first

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-0609 — 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-0609 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