dbcve.org
Acrobat ReaderApplication · Adobe

CVE-2013-2734

HIGH · 10.0 CVSS v2.0 Published 2013-05-16
Patch available
A vendor patch is available. No clean upgrade release — apply the published patch.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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.5, 10.x before 10.1.7, and 11.x before 11.0.03 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2013-2718, CVE-2013-2719, CVE-2013-2720, CVE-2013-2721, CVE-2013-2722, CVE-2013-2723, CVE-2013-2725, CVE-2013-2726, CVE-2013-2731, CVE-2013-2732, CVE-2013-2735, CVE-2013-2736, CVE-2013-3337, CVE-2013-3338, CVE-2013-3339, CVE-2013-3340, and CVE-2013-3341.

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

Adobe Reader and Acrobat contain a memory corruption vulnerability (CVSS 10) that allows remote attackers to execute arbitrary code or cause denial of service. The vulnerability affects versions 9.x before 9.5.5, 10.x before 10.1.7, and 11.x before 11.0.03. The specific attack vector is not detailed in the available description.

MitigationUpdate Adobe Reader and Acrobat to versions 9.5.5, 10.1.7, or 11.0.03 or later to remediate this vulnerability. Organizations should deploy these updates via their patch management infrastructure.

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

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
    Open Control Panel > Programs and Features, or check for the presence of Adobe Reader in C:\Program Files\Adobe\Adobe Reader X\ (where X is the version number). On Linux, check for /opt/Adobe or ~/.adobe directories.
    Affected if Adobe Reader is present on the system
  2. Check if Adobe Acrobat is installed
    Open Control Panel > Programs and Features, or check for the presence of Adobe Acrobat in C:\Program Files\Adobe\Adobe Acrobat X\ (where X is the version number).
    Affected if Adobe Acrobat is present on the system
  3. Determine the installed Adobe Reader version
    Navigate to the Adobe Reader installation directory, right-click on the AcroRd32.exe file, select Properties, and check the Details tab for the Product Version. Alternatively, open Adobe Reader and go to Help > About Adobe Reader.
    Affected if The version is 9.0 through 9.4.x, or 10.x before 10.1.7, or 11.x before 11.0.03
  4. Determine the installed Adobe Acrobat version
    Navigate to the Adobe Acrobat installation directory, right-click on the AcroTray.exe or AcroBroker.exe file, select Properties, and check the Details tab for the Product Version. Alternatively, open Adobe Acrobat and go to Help > About Adobe Acrobat.
    Affected if The version is 9.0 through 9.4.x, or 10.x before 10.1.7, or 11.x before 11.0.03

A system is affected if Adobe Reader or Adobe Acrobat is installed and the version matches 9.0-9.4.x, 10.x before 10.1.7, or 11.x before 11.0.03.

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
Patch available Apply the vendor patch
Vendor patch www.adobe.com →
Interim mitigation

Update Adobe Reader and Acrobat to versions 9.5.5, 10.1.7, or 11.0.03 or later to remediate this vulnerability. Organizations should deploy these updates via their patch management infrastructure.

Recommended fix High confidence

Adobe Reader/Acrobat 9.5.5+ (for 9.x), 10.1.7+ (for 10.x), or 11.0.03+ (for 11.x)

  1. Identify the currently installed Adobe Reader or Acrobat version
  2. For 9.x versions: upgrade to Adobe Reader/Acrobat 9.5.5 or later
  3. For 10.x versions: upgrade to Adobe Reader/Acrobat 10.1.7 or later
  4. For 11.x versions: upgrade to Adobe Reader/Acrobat 11.0.03 or later
  5. Download the appropriate fixed version from the official Adobe website or your organization's software distribution channel
  6. Install the update following standard installation procedures
  7. Verify the installed version matches the target fixed release
Caveat Upgrading major versions may introduce UI changes; ensure compatibility with existing workflows and dependencies

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

Fix this in Acrobat Reader Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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