dbcve.org
Acrobat ReaderApplication · Adobe

CVE-2013-3341

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-2734, CVE-2013-2735, CVE-2013-2736, CVE-2013-3337, CVE-2013-3338, CVE-2013-3339, and CVE-2013-3340.

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 attackers to execute arbitrary code or cause denial of service. The flaw affects versions 9.x before 9.5.5, 10.x before 10.1.7, and 11.x before 11.0.03. This is part of a large set of vulnerabilities disclosed in May 2013.

MitigationUpdate Adobe Reader and Acrobat to versions 9.5.5, 10.1.7, or 11.0.03 or later. If immediate patching is not possible, restrict access to untrusted PDF sources and disable JavaScript in Adobe Reader settings as a defense-in-depth measure.

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. Identify installed Adobe product
    Check system for Adobe Reader or Adobe Acrobat installation. Common locations: Windows: Program Files\Adobe\Acrobat [Version] or Program Files\Adobe\Reader [Version], Mac: /Applications/Adobe Reader.app or /Applications/Adobe Acrobat.app
    Affected if Adobe Reader or Adobe Acrobat is installed on the system
  2. Determine exact version number
    Open Adobe Reader/Acrobat, then go to Help > About Adobe Reader/Acrobat to display the exact version number. Alternatively, right-click the executable file, select Properties, and view the File Version details.
    Affected if Version displayed is 9.x before 9.5.5, 10.x before 10.1.7, or 11.x before 11.0.03
  3. Verify product type matches affected list
    Confirm whether the installed product is Adobe Reader or Adobe Acrobat. Both product lines are affected per the CVE.
    Affected if Product is Adobe Reader or Adobe Acrobat with an affected version number

A user is affected if Adobe Reader or Adobe Acrobat is installed and the version falls within 9.x before 9.5.5, 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. If immediate patching is not possible, restrict access to untrusted PDF sources and disable JavaScript in Adobe Reader settings as a defense-in-depth measure.

Recommended fix High confidence

Adobe Reader/Acrobat 9.5.5 or later (also addresses 10.x to 10.1.7+ and 11.x to 11.0.03+)

  1. 1. Verify current Adobe Reader/Acrobat version by opening the application and navigating to Help > About Adobe Reader/Acrobat
  2. 2. Download Adobe Reader 9.5.5 or later from the official Adobe website (get.adobe.com/reader) or your organization's software distribution center
  3. 3. Close all Adobe Reader/Acrobat instances and any web browsers that may have PDF plugins loaded
  4. 4. Run the installer with appropriate administrator privileges
  5. 5. Follow the on-screen installation prompts, accepting the license agreement
  6. 6. After installation completes, restart any affected applications
  7. 7. Verify the updated version by checking Help > About Adobe Reader/Acrobat confirms version 9.5.5 or higher

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

Fix this in Acrobat Reader Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the patch applied

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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