dbcve.org
AcrobatApplication · Adobe

CVE-2013-0617

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-0606, CVE-2013-0612, CVE-2013-0615, 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 vulnerability allows attackers to execute arbitrary code via unspecified vectors through memory corruption.

MitigationApply vendor patches to update Adobe Reader and Acrobat to versions 9.5.3, 10.1.5, 11.0.1 or later; alternatively, disable JavaScript execution in Adobe Reader as a temporary mitigation.

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. Identify installed Adobe product
    Check for Adobe Reader or Adobe Acrobat installation. On Windows, look in Program Files for Adobe folders, or check registry keys under HKLM\SOFTWARE\Adobe\Adobe Acrobat or HKLM\SOFTWARE\Adobe\Adobe Reader. On Mac, check /Applications for Adobe Acrobat or Adobe Reader apps.
    Affected if Either Adobe Reader or Adobe Acrobat is installed on the system
  2. Retrieve installed version number
    Open Adobe Reader or Acrobat, then navigate to Help > About Adobe Reader/Acrobat to display the exact version number. Alternatively, query the Windows registry value 'Version' or 'ProductVersion' under the product's registry key.
    Affected if A version number is displayed that can be compared against vulnerable ranges
  3. Compare against vulnerable version ranges
    Match your installed version against the affected ranges: 9.x versions before 9.5.3, 10.x versions before 10.1.5, and 11.x versions before 11.0.1. For version 9.x, any version from 9.0 through 9.4.x is affected.
    Affected if The installed version falls within 9.0 to 9.4.x, 10.0 to 10.1.4, or 11.0.0

A system is affected if Adobe Reader or Acrobat is installed with a version in the ranges 9.0-9.4.x, 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

Apply vendor patches to update Adobe Reader and Acrobat to versions 9.5.3, 10.1.5, 11.0.1 or later; alternatively, disable JavaScript execution in Adobe Reader as a temporary mitigation.

Recommended fix High confidence

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

  1. 1. Identify the exact Adobe Acrobat or Adobe Reader version installed on the system via Help > About menu
  2. 2. Download the latest version of Adobe Acrobat or Adobe Reader from the official Adobe website (get.adobe.com/reader)
  3. 3. Uninstall the current version of Adobe Acrobat or Adobe Reader from the system
  4. 4. Install the upgraded version: for 9.x line upgrade to 9.5.3 or later, for 10.x upgrade to 10.1.5 or later, for 11.x upgrade to 11.0.1 or later
  5. 5. Verify the installation by checking Help > About to confirm the version matches the target fixed release
  6. 6. Apply any additional Adobe security updates or patches released after the base fixed versions
Caveat Minor: Upgrading major versions may introduce UI changes; ensure compatibility with any existing PDF workflows or integrations before deploying broadly

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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