CVE-2013-3357
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 · uneditedInteger overflow in Adobe Reader and Acrobat before 10.1.8 and 11.x before 11.0.04 on Windows and Mac OS X allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2013-3358.
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 confidenceInteger overflow vulnerability in Adobe Reader and Acrobat on Windows and Mac OS X that allows attackers to execute arbitrary code via unspecified vectors.
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= 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= 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.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe productCheck if Adobe Reader or Adobe Acrobat is installed on the system. On Windows, look in Program Files for 'Adobe' folder or check Add/Remove Programs. On Mac, check /Applications for Adobe Acrobat or Adobe Reader.Affected if Either Adobe Reader or Adobe Acrobat is installed
-
Determine Adobe Reader version on WindowsOpen Adobe Reader, go to Help > About Adobe Reader. The version number displayed in the dialog window is the installed version.Affected if Version shown 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
-
Determine Adobe Acrobat version on WindowsOpen Adobe Acrobat, go to Help > About Adobe Acrobat. The version number displayed in the dialog window is the installed version.Affected if Version shown 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
-
Determine version on Mac OS XOpen Adobe Reader or Adobe Acrobat, then go to the application menu (Adobe Reader or Adobe Acrobat) and select About. The version number is displayed in the about dialog.Affected if Version shown 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
You are affected if Adobe Reader or Adobe Acrobat version is 10.0, 10.0.x, 10.1.x (where x is 0-7), or 10.1.7 installed on Windows or Mac OS X.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe Reader to version 10.1.8 or 11.0.04 or later to patch the integer overflow vulnerability.
Adobe Acrobat and Reader 10.1.8 (or latest 10.x release); Adobe Acrobat and Reader 11.0.04 or later if applicable
- 1. Verify the currently installed Adobe Acrobat or Adobe Reader version by opening the application, going to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. If the version is 10.0, 10.0.1, 10.0.2, or 10.0.3, the system is vulnerable.
- 3. Download the fixed version from the official Adobe website or your organization's software distribution center.
- 4. For Adobe Acrobat 10.x users: Upgrade to version 10.1.8 or later.
- 5. For Adobe Reader 10.x users: Upgrade to version 10.1.8 or later.
- 6. Ensure all patches are applied and verify the version number after updating.
- 7. Consider updating to the latest available version of Adobe Acrobat/Reader for additional security improvements.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-3357 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-3357 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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