dbcve.org
AcrobatApplication · Adobe

CVE-2013-3352

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-3354 and CVE-2013-3355.

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 (versions before 10.1.8 and 11.x before 11.0.04) allows attackers to execute arbitrary code or cause denial of service via unspecified vectors.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.8 or later (for v10) or 11.0.04 or later (for v11) to remediate the memory corruption 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. Confirm Adobe product is installed
    Check for Adobe Acrobat or Adobe Reader installation: On Windows, look in C:\Program Files\Adobe or C:\Program Files (x86)\Adobe for acrobat.exe or ar*.exe files. On Mac, check /Applications for Adobe Acrobat or Adobe Reader.
    Affected if Either Adobe Acrobat or Adobe Reader is installed on Windows or Mac OS X
  2. Identify the installed product and version
    On Windows: Open the application, go to Help > About Adobe Acrobat/Reader to see the version number. Alternatively, check the Windows Registry at HKLM\SOFTWARE\Adobe\Adobe Acrobat\ or HKLM\SOFTWARE\Adobe\Adobe Reader\ for the version value.
    Affected if The installed version matches any of: Acrobat 10.0 through 10.1.7, Reader 10.0 through 10.1.3, or Reader 11.0 through 11.0.3
  3. Verify the exact version number
    Compare the identified version against the affected list. For Adobe Acrobat: versions 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 are affected. For Adobe Reader: versions 10.0, 10.0.1, 10.0.2, 10.0.3, 10.1, 10.1.1, 10.1.2, 10.1.3, 11.0, 11.0.1, 11.0.2, 11.0.3 are affected.
    Affected if The version is any of the listed affected versions (10.0.x, 10.1.x up to 10.1.7, or 11.0.x up to 11.0.3)

If Adobe Acrobat or Reader is installed and the version falls within 10.0.x through 10.1.7 (for Acrobat), 10.0.x through 10.1.3 or 11.0.x through 11.0.3 (for Reader), 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 later (for v10) or 11.0.04 or later (for v11) to remediate the memory corruption vulnerability.

Recommended fix High confidence

Adobe Acrobat 10.1.8 or Adobe Acrobat Reader 11.0.04 (depending on product line)

  1. 1. Identify whether Adobe Acrobat or Adobe Reader is installed, and note the exact version number (help > about)
  2. 2. For Adobe Acrobat 10.x users: Download Adobe Acrobat 10.1.8 from the official Adobe website or your organization's software distribution portal
  3. 3. For Adobe Acrobat Reader 11.x users: Download Adobe Acrobat Reader 11.0.04 from the official Adobe website or your organization's software distribution portal
  4. 4. Close all Adobe applications (Acrobat or Reader) before installing the update
  5. 5. Run the installer for the appropriate fixed version
  6. 6. Verify the installation was successful by checking the version number (help > about) shows 10.1.8 for v10 or 11.0.04 for v11
Caveat Upgrading Adobe software may require acceptance of new license terms; ensure compatibility with any dependent workflows or integrations before deploying

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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