dbcve.org
Acrobat ReaderApplication · Adobe

CVE-2013-3351

HIGH · 10.0 CVSS v2.0 Published 2013-09-12
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
Multiple stack-based buffer overflows in Adobe Reader and Acrobat before 10.1.8 and 11.x before 11.0.04 on Windows and Mac OS X allow attackers to execute arbitrary code via unspecified vectors.

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

Stack-based buffer overflow vulnerabilities in Adobe Reader and Acrobat versions before 10.1.8 and 11.0.04 allow remote attackers to execute arbitrary code via unspecified vectors on Windows and Mac OS X systems.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.8 or 11.0.04 or later to remediate the 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
Acrobat ReaderApplication
Affected:= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.1= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7
AcrobatApplication
Affected:= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.1= 10.1.1= 10.1.2= 10.1.3= 10.1.4= 10.1.5= 10.1.6= 10.1.7

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. Confirm Adobe Reader is installed
    Check for Adobe Reader installation: On Windows, look in Program Files for Adobe folder or check Add/Remove Programs. On Mac, check /Applications for Adobe Reader.app
    Affected if Adobe Reader is present on the system
  2. Determine Adobe Reader version
    On Windows: Right-click the Adobe Reader shortcut, select Properties, and view the version in the Details tab. Alternatively, open Adobe Reader, go to Help > About Adobe Reader. On Mac: Right-click Adobe Reader.app, select Get Info, or open Help > About Adobe Reader
    Affected if Version is 10.0, 10.0.1, 10.0.2, 10.0.3, 10.1, 10.1.1, 10.1.2, 10.1.3, 10.1.4, 10.1.5, 10.1.6, or 10.1.7
  3. Confirm Adobe Acrobat is installed
    Check for Adobe Acrobat installation: On Windows, look in Program Files for Adobe Acrobat folder. On Mac, check /Applications for Adobe Acrobat.app
    Affected if Adobe Acrobat is present on the system
  4. Determine Adobe Acrobat version
    On Windows: Right-click the Adobe Acrobat shortcut, select Properties, and view the version in the Details tab. Alternatively, open Adobe Acrobat, go to Help > About Adobe Acrobat. On Mac: Right-click Adobe Acrobat.app, select Get Info, or open Help > About Adobe Acrobat
    Affected if Version is 10.0, 10.0.1, 10.0.2, 10.0.3, 10.1, 10.1.1, 10.1.2, 10.1.3, 10.1.4, 10.1.5, 10.1.6, or 10.1.7

The system is affected if Adobe Reader or Adobe Acrobat version 10.0 through 10.1.7 is installed on Windows or Mac OS X.

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 version 10.1.8 or 11.0.04 or later to remediate the vulnerability.

Recommended fix High confidence

Adobe Reader/Acrobat 10.1.8 or later, or 11.0.04 or later

  1. 1. Close all Adobe Reader or Acrobat instances running on the system
  2. 2. Navigate to the official Adobe download page or use your organization's software distribution system
  3. 3. Download Adobe Reader 10.1.8 or later (for Reader 10.x users)
  4. 4. Download Adobe Acrobat 10.1.8 or later (for Acrobat 10.x users)
  5. 5. Alternatively, upgrade to Adobe Reader/Acrobat 11.0.04 or later for the 11.x product line
  6. 6. Run the installer with appropriate administrator privileges
  7. 7. Restart the system after installation completes
  8. 8. Verify the installed version by opening Adobe Reader/Acrobat and checking Help > About
Caveat Adobe security updates typically have minimal breaking changes; ensure compatibility with any existing PDF workflows or plugins

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,780
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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