dbcve.org
AcrobatApplication · Adobe

CVE-2013-3355

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
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 or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2013-3352 and CVE-2013-3354.

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

Memory corruption vulnerability in Adobe Reader and Acrobat on Windows and Mac OS X allowing arbitrary code execution or denial of service. The vulnerability exists before versions 10.1.8 and 11.0.04 and involves unspecified vectors leading to memory corruption.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.8 or 11.0.04 or later to remediate this critical 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
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
Acrobat ReaderApplication
Affected:= 11.0= 11.0.1= 11.0.2= 11.0.3= 10.0= 10.0.1= 10.0.2= 10.0.3= 10.1= 10.1.1= 10.1.2= 10.1.3

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 Adobe Reader version
    Open Adobe Reader, go to Help > About Adobe Reader. Note the version number displayed (e.g., 10.1.7 or 11.0.03).
    Affected if The installed version is 10.0 through 10.1.7, or 11.0 through 11.0.03 (any version before 10.1.8 or 11.0.04).
  2. Check Adobe Acrobat version
    Open Adobe Acrobat, go to Help > About Adobe Acrobat. Note the version number displayed.
    Affected if The installed version is 10.0 through 10.1.7 (any version before 10.1.8 for Acrobat).
  3. Verify product type and platform
    Confirm whether the installed product is Adobe Reader or Adobe Acrobat, and verify the operating system is Windows or Mac OS X (the vulnerability affects these platforms only).
    Affected if The product is Adobe Reader or Adobe Acrobat on Windows or Mac OS X, and the version falls in the affected ranges.

If Adobe Reader or Adobe Acrobat version is 10.1.7 or earlier, or 11.0.03 or earlier on Windows or Mac OS X, the environment is affected by this memory corruption vulnerability.

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 this critical vulnerability.

Recommended fix High confidence

Adobe Acrobat 10.1.8 (for 10.0.x) or Adobe Reader 11.0.04 (for 11.0.x)

  1. 1. Identify 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 matches the affected versions: Acrobat 10.0 through 10.0.3, or Reader 11.0 through 11.0.3.
  3. 3. For Adobe Acrobat 10.0.x users: Download Adobe Acrobat 10.1.8 from the official Adobe website or your organization's software distribution portal.
  4. 4. For Adobe Reader 11.0.x users: Download Adobe Reader 11.0.04 from the official Adobe website or your organization's software distribution portal.
  5. 5. Close all Adobe applications and any applications that integrate with Adobe PDF functionality.
  6. 6. Run the downloaded installer with appropriate administrator privileges.
  7. 7. Follow the on-screen installation prompts to complete the update.
  8. 8. After installation, verify the new version by checking Help > About to confirm the version matches the expected fixed release (10.1.8 for Acrobat 10.x, 11.0.04 for Reader 11.x).
Caveat Security update may require acceptance of new license terms; ensure compatibility with existing PDF-dependent workflows before deployment

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

Fix this in Acrobat 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-3355 — 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-3355 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