CVE-2013-0612
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 · uneditedBuffer overflow in Adobe Reader and Acrobat 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1 allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2013-0606, CVE-2013-0615, CVE-2013-0617, and CVE-2013-0621.
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 confidenceBuffer overflow vulnerability in Adobe Reader and Acrobat versions 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1 allows remote attackers to execute arbitrary code via unspecified vectors. This is a critical severity (CVSS 10) flaw distinct from related Adobe vulnerabilities (CVE-2013-0606, CVE-2013-0615, CVE-2013-0617, CVE-2013-0621).
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= 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= 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.4CVSS 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.
-
Confirm Adobe Acrobat or Acrobat Reader is installedOn Windows, check Start menu for Adobe Acrobat or Adobe Reader entry, or check Program Files for Adobe folder. On Mac, check /Applications for Adobe Acrobat or Adobe Reader.Affected if Either Adobe Acrobat or Adobe Acrobat Reader is present on the system
-
Locate the product versionOpen the application, then go to Help > About Adobe Acrobat (or About Adobe Reader). The version number displays in the dialog window.Affected if Version cannot be determined or product is not installed
-
Compare version 9.x against vulnerable rangeIf version starts with 9, check if it is 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, or 9.4. These versions are all affected.Affected if Version is 9.0 through 9.4 (any minor version listed in the affected products)
-
Compare version 10.x against vulnerable rangeIf version starts with 10, extract the full version (for example, 10.1.4). Compare numerically to 10.1.5. Versions below 10.1.5 are affected.Affected if Version starts with 10 and is earlier than 10.1.5 (for example, 10.0, 10.1, 10.1.4)
-
Compare version 11.x against vulnerable rangeIf version starts with 11, extract the full version (for example, 11.0.0). Compare numerically to 11.0.1. Versions below 11.0.1 are affected.Affected if Version starts with 11 and is earlier than 11.0.1 (for example, 11.0.0)
The system is affected if Adobe Acrobat or Acrobat Reader version is 9.0-9.4, 10.x before 10.1.5, or 11.x before 11.0.1.
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 · scopedApply vendor-supplied patches by upgrading Adobe Reader and Acrobat to version 9.5.3, 10.1.5, 11.0.1 or later. Consider disabling JavaScript in Adobe products as an interim compensating control until patching is complete.
Adobe Reader/Acrobat 9.5.3+, 10.1.5+, or 11.0.1+ (depending on your major version branch)
- 1. Identify the currently installed Adobe Acrobat or Adobe Reader version by opening the application and navigating to Help > About (or About Adobe Reader/Acrobat)
- 2. For Adobe Reader 9.x users: Upgrade to version 9.5.3 or later
- 3. For Adobe Reader 10.x users: Upgrade to version 10.1.5 or later
- 4. For Adobe Reader 11.x users: Upgrade to version 11.0.1 or later
- 5. For Adobe Acrobat 9.x users: Upgrade to version 9.5.3 or later
- 6. For Adobe Acrobat 10.x users: Upgrade to version 10.1.5 or later
- 7. For Adobe Acrobat 11.x users: Upgrade to version 11.0.1 or later
- 8. Download the appropriate updated version from the official Adobe website or your organization's software distribution channel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0612 — 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-0612 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