dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 24 Mar 2022.
AcrobatApplication · Adobe

CVE-2013-3346

CRITICAL · 9.8 CVSS v3.1 Published 2013-08-30
Fix available
A fix is available. Upgrade to 9.5.5 / 10.1.7 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS 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.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-2734, 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 · high confidence

Adobe Reader and Acrobat contain a memory corruption vulnerability allowing remote code execution or 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, and is distinct from other 2013 Adobe vulnerabilities.

MitigationUpgrade Adobe Reader and Acrobat to version 9.5.5 or later for 9.x, 10.1.7 or later for 10.x, or 11.0.03 or later for 11.x. Alternatively, disable or restrict PDF handling in untrusted contexts until patches can be applied.

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.5.5>= 10.0, < 10.1.7>= 11.0, < 11.0.03
Acrobat ReaderApplication
Affected:>= 9.0, < 9.5.5>= 10.0, < 10.1.7>= 11.0, < 11.0.03

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
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 PDF product
    On Windows, open Control Panel > Programs and Features (or Add or Remove Programs on older systems) and look for Adobe Acrobat or Adobe Reader. On macOS, open Finder > Applications and check for Adobe Acrobat or Adobe Reader.
    Affected if Neither Adobe Acrobat nor Adobe Reader is installed - not affected
  2. Determine the exact version number
    For Adobe Reader: Open the application, go to Help > About Adobe Reader. For Adobe Acrobat: Open the application, go to Help > About Adobe Acrobat. Note the full version number displayed (e.g., 9.5.4, 10.1.6, 11.0.02).
    Affected if Version cannot be determined - status unknown, further investigation needed
  3. Compare version against affected ranges
    Match your installed version to these ranges: 9.x versions before 9.5.5 (such as 9.5.4, 9.5.3, 9.4.x, 9.3.x), 10.x versions before 10.1.7 (such as 10.1.6, 10.1.5, 10.0.x), or 11.x versions before 11.0.03 (such as 11.0.02, 11.0.01, 11.0.00).
    Affected if Installed version falls within 9.0 to <9.5.5, OR 10.0 to <10.1.7, OR 11.0 to <11.0.03 - environment is affected

Your environment is affected if Adobe Acrobat or Adobe Reader is installed with a version in the ranges 9.0 to less than 9.5.5, 10.0 to less than 10.1.7, or 11.0 to less than 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
Upgrade available Upgrade to 9.5.5 / 10.1.7 / 11.0.03 or later
Fixed in 9.5.510.1.711.0.03
Interim mitigation

Upgrade Adobe Reader and Acrobat to version 9.5.5 or later for 9.x, 10.1.7 or later for 10.x, or 11.0.03 or later for 11.x. Alternatively, disable or restrict PDF handling in untrusted contexts until patches can be applied.

Recommended fix High confidence

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

  1. 1. Determine the currently installed Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
  2. 2. Identify which major version branch you are using (9.x, 10.x, or 11.x).
  3. 3. Download the appropriate fixed version from the official Adobe website: For 9.x users, download version 9.5.5; For 10.x users, download version 10.1.7; For 11.x users, download version 11.0.03.
  4. 4. Close all Adobe Acrobat or Reader instances and any browser instances that may have PDF plugins enabled.
  5. 5. Run the installer for the appropriate fixed version and follow the on-screen prompts to complete the upgrade.
  6. 6. After installation, verify the new version by checking Help > About to confirm the version matches the expected fixed release.
  7. 7. Ensure any third-party PDF plugins or extensions are compatible with the new version.
Caveat Upgrading may affect compatibility with older third-party PDF plugins or scripts; test in a non-production environment if workflows depend on specific plugin versions.

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

Fix this in Acrobat Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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