CVE-2013-0616
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 · uneditedAdobe Reader and Acrobat 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2012-1530, CVE-2013-0601, CVE-2013-0605, CVE-2013-0619, CVE-2013-0620, and CVE-2013-0623.
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 confidenceMemory corruption vulnerability in Adobe Reader and Acrobat allowing arbitrary code execution or denial of service. Affects versions 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1. Exploitation occurs through unspecified vectors leading to memory corruption.
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.
-
Check Adobe Reader version on WindowsOpen Windows Registry and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-AA1000000001} (for Reader) and look at the DisplayVersion value, or right-click acrord32.exe/acrord64.exe in the Reader installation folder (usually C:\Program Files\Adobe\Reader X.X\Reader\) and select Properties > Details to see the File VersionAffected if DisplayVersion or File Version 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 (any 9.x version before 9.5.3)
-
Check Adobe Acrobat version on WindowsOpen Windows Registry and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-A70000000001} (for Acrobat) and look at the DisplayVersion value, or right-click acrobat.exe in the Acrobat installation folder (usually C:\Program Files\Adobe\Acrobat X.X\) and select Properties > Details to see the File VersionAffected if DisplayVersion or File Version 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 (any 9.x version before 9.5.3)
-
Check for version 10.x or 11.x installationsIf Reader or Acrobat is version 10.x, verify the exact minor version via Help > About Adobe Reader/Acrobat menu, or check the File Version of the main executable; same for version 11.xAffected if Version is 10.0 through 10.1.4 (any 10.x before 10.1.5) or 11.0.0 (11.x before 11.0.1)
The environment is affected if any installed Adobe Reader or Adobe Acrobat version is 9.x before 9.5.3, 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 updating Adobe Reader and Acrobat to version 9.5.3, 10.1.5, 11.0.1 or later. Prioritize patching given CVSS 10 severity and active exploitation potential.
Adobe Acrobat/Reader 9.5.3 (for 9.x users); 10.1.5 (for 10.x users); 11.0.1 (for 11.x users)
- 1. Identify the current installed version of Adobe Acrobat or Adobe Reader by opening the application and navigating to 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 from the official Adobe website or your organization's software distribution channel
- 3. For Adobe 10.x versions (10.0 through 10.1.4), download and install Adobe Acrobat/Reader 10.1.5
- 4. For Adobe 11.x versions (11.0.0), download and install Adobe Acrobat/Reader 11.0.1
- 5. Restart the Adobe application after installation completes
- 6. Verify the version update was successful by checking Help > About again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0616 — 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-0616 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