CVE-2013-0604
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 · uneditedHeap-based buffer 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-0603.
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 confidenceHeap-based buffer 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.
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.
-
Verify Adobe Reader installation and locate executableCheck for Adobe Reader in typical installation paths such as C:\Program Files\Adobe\Reader [version]\Reader\AcroRd32.exe, or use Windows Installer (wmic product get name,version) or registry (HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*) to enumerate installed Adobe products.Affected if Adobe Reader is not installed on the system.
-
Determine installed Adobe Reader versionRight-click AcroRd32.exe, select Properties, then view the Details tab for Product Version, or run: AcroRd32.exe /version, or use PowerShell: (Get-Item 'C:\Program Files\Adobe\Reader [version]\Reader\AcroRd32.exe').VersionInfo.ProductVersion.Affected if The detected version cannot be determined or the product is not Adobe Reader.
-
Verify Adobe Acrobat installation and locate executableCheck for Adobe Acrobat in typical installation paths such as C:\Program Files\Adobe\Acrobat [version]\Acrobat\Acrobat.exe, or use Windows Installer or registry to enumerate installed Adobe Acrobat products.Affected if Adobe Acrobat is not installed on the system.
-
Determine installed Adobe Acrobat versionRight-click Acrobat.exe, select Properties, then view the Details tab for Product Version, or run: Acrobat.exe /version, or use PowerShell to retrieve the file version of the main executable.Affected if The detected version cannot be determined or the product is not Adobe Acrobat.
-
Compare version against affected rangesFor Adobe Reader: affected if version is 9.0 through 9.4.x, 10.0 through 10.1.x before 10.1.5, or 11.0 before 11.0.1. For Adobe Acrobat: affected if version is 9.0 through 9.4.x, 10.0 through 10.1.x before 10.1.5, or 11.0 before 11.0.1.Affected if The installed version falls within 9.0-9.4.x, 10.x before 10.1.5, or 11.x before 11.0.1.
The environment is affected if Adobe Reader or Adobe Acrobat is installed with a version between 9.0 and 9.4.x, between 10.0 and 10.1.4, or between 11.0 and 11.0.0.
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 patches to reach version 9.5.3, 10.1.5, or 11.0.1 or later. Until patched, exercise caution with untrusted PDF files and consider disabling JavaScript in Adobe Reader.
Adobe Acrobat/Reader 9.5.3 (for 9.x) | 10.1.5 (for 10.x) | 11.0.1 (for 11.x)
- 1. Identify the current installed version of Adobe Acrobat or Adobe Reader (Help > About Adobe Acrobat/Reader)
- 2. For Adobe 9.x versions (9.0, 9.1, 9.1.1, 9.1.2), download and install Adobe Acrobat/Reader 9.5.3 or later from the Adobe website or use the application's Help > Check for Updates feature
- 3. For Adobe 10.x versions, upgrade to version 10.1.5 or later
- 4. For Adobe 11.x versions, upgrade to version 11.0.1 or later
- 5. After installation, restart the Adobe application
- 6. Verify the version update by checking Help > About to confirm the installed version contains the security patch
- 7. Ensure automatic updates are enabled for future security patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0604 — 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-0604 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