dbcve.org
AcrobatApplication · Adobe

CVE-2013-0611

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
Adobe 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-0614, 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 confidence

Adobe Reader and Acrobat contain a logic error that allows attackers to execute arbitrary code. This vulnerability affects versions 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1. The attack vector is through unspecified vectors, indicating it may be triggered by specially crafted PDF files or content processed by the software.

MitigationImmediately update Adobe Reader and Acrobat to version 9.5.3, 10.1.5, or 11.0.1 or later. Given the CVSS 10 severity, prioritize patching all affected systems as this vulnerability can lead to complete system compromise.

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
    Open Adobe Reader or Adobe Acrobat, then go to Help > About Adobe Reader or About Adobe Acrobat to view the version number. Alternatively, check Add/Remove Programs or the Windows Registry under HKLM\SOFTWARE\Adobe for the version key.
    Affected if The product name is Adobe Reader or Adobe Acrobat with any version shown.
  2. Verify Adobe Reader version
    If using Adobe Reader, confirm the exact version number displayed in the About dialog matches one of the affected versions: 9.0 through 9.4.x, or 10.x before 10.1.5, or 11.x before 11.0.1.
    Affected if The installed Adobe Reader version is 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, or any 10.x version before 10.1.5, or any 11.x version before 11.0.1.
  3. Verify Adobe Acrobat version
    If using Adobe Acrobat, confirm the exact version number displayed in the About dialog matches one of the affected versions: 9.0 through 9.4.x.
    Affected if The installed Adobe Acrobat version is 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, or 9.4.
  4. Check for vulnerable PDF handling
    While this CVE is triggered by specially crafted PDF files, the detection focus is on version. No specific configuration or feature needs to be enabled for the vulnerability to exist; the flaw is in the core software logic.
    Affected if The installed version is within the affected ranges regardless of specific settings.

A system is affected if Adobe Reader or Adobe Acrobat version is 9.0 through 9.4.x, 10.x before 10.1.5, or 11.x before 11.0.1.

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

Immediately update Adobe Reader and Acrobat to version 9.5.3, 10.1.5, or 11.0.1 or later. Given the CVSS 10 severity, prioritize patching all affected systems as this vulnerability can lead to complete system compromise.

Recommended fix High confidence

Adobe Acrobat/Reader 9.5.3+ (for 9.x users), 10.1.5+ (for 10.x users), or 11.0.1+ (for 11.x users); or migrate to current Adobe Acrobat subscription for ongoing security updates

  1. 1. Verify the currently installed Adobe Acrobat or Adobe Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader or About Adobe Acrobat
  2. 2. Determine if the installed version is one of the affected versions: 9.0, 9.1, 9.1.1, 9.1.2 (for 9.x line), or any version before 9.5.3, 10.1.5, or 11.0.1
  3. 3. If running an affected version, download the latest Adobe Acrobat Reader or Adobe Acrobat from the official Adobe website (get.adobe.com/reader or get.adobe.com/acrobat)
  4. 4. Close all Adobe applications and any web browsers with PDF plugins before installation
  5. 5. Run the downloaded installer with administrator privileges
  6. 6. Follow the on-screen installation prompts to complete the upgrade
  7. 7. After installation, restart the computer to ensure all components are properly initialized
  8. 8. Verify the new version by checking Help > About to confirm the installed version is 9.5.3 or later (for 9.x), 10.1.5 or later (for 10.x), or 11.0.1 or later (for 11.x)
Caveat Legacy standalone installers may not be available for old versions; current Adobe products require a subscription; old configurations 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
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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 locally
dbcve dependency scanner

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