CVE-2013-3358
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-3357.
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 confidenceInteger overflow vulnerability in Adobe Reader and Acrobat on Windows and Mac OS X allows remote attackers to execute arbitrary code via unspecified vectors. The flaw exists in versions prior to 10.1.8 and 11.x before 11.0.04, where improper integer handling can lead to heap-based memory corruption enabling code execution.
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= 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.3CVSS 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 if Adobe Acrobat is installedOn Windows, check Program Files\Adobe\Acrobat <version> folder or open Acrobat and go to Help > About Adobe Acrobat. On Mac, check /Applications/Adobe Acrobat <version>.appAffected if Adobe Acrobat version is 10.0.x, 10.1.x through 10.1.7, or 11.0.x through 11.0.03
-
Identify if Adobe Reader is installedOn Windows, check Program Files\Adobe\Reader <version> folder or open Reader and go to Help > About Adobe Reader. On Mac, check /Applications/Adobe Reader <version>.appAffected if Adobe Reader version is 10.0.x, 10.1.x through 10.1.7, or 11.0.x through 11.0.03
-
Verify the exact version numberOpen the application, then go to Help > About (Adobe Acrobat or Adobe Reader). The version displays as "10.x.x" or "11.x.x" in the dialog window.Affected if Version shown is below 10.1.8 for 10.x branch or below 11.0.04 for 11.x branch
-
Confirm operating system is Windows or Mac OS XCheck the operating system of the machine where Adobe product is installed (this vulnerability affects only Windows and Mac OS X, not Linux).Affected if Operating system is Windows or Mac OS X and Adobe version falls within affected ranges
Your environment is affected if Adobe Acrobat or Adobe Reader version is 10.0 through 10.1.7 or 11.0 through 11.0.03 running 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 and Acrobat to version 10.1.8 or later for the 10.x branch, or 11.0.04 or later for the 11.x branch to remediate this vulnerability.
Adobe Acrobat/Reader 10.1.8 for version 10.x line, or 11.0.04 for version 11.x line
- Identify the currently installed Adobe Acrobat or Adobe Reader version on the system
- Close all running Adobe Acrobat or Adobe Reader instances
- Download Adobe Acrobat 10.1.8 (for version 10.x) or 11.0.04 (for version 11.x) from the official Adobe website or your organization's software distribution center
- Run the installer and follow the prompts to upgrade the software
- Restart the computer if prompted by the installer
- Verify the installation was successful by checking Help > About in Adobe Acrobat/Reader to confirm the version matches the fixed release (10.1.8 or 11.0.04)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2013-3358 — 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-3358 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