CVE-2013-2725
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.5, 10.x before 10.1.7, and 11.x before 11.0.03 allow attackers to execute arbitrary code or cause a denial of service (memory corruption) via unspecified vectors, a different vulnerability than CVE-2013-2718, CVE-2013-2719, CVE-2013-2720, CVE-2013-2721, CVE-2013-2722, CVE-2013-2723, CVE-2013-2726, CVE-2013-2731, CVE-2013-2732, CVE-2013-2734, CVE-2013-2735, CVE-2013-2736, CVE-2013-3337, CVE-2013-3338, CVE-2013-3339, CVE-2013-3340, and CVE-2013-3341.
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 versions 9.x before 9.5.5, 10.x before 10.1.7, and 11.x before 11.0.03 allows attackers to achieve arbitrary code execution or cause denial of service via unspecified attack 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.
-
Identify installed Adobe productOpen Adobe Reader or Acrobat and navigate to Help > About Adobe Reader/Acrobat, or check Programs and Features in Control Panel for the installed product name and versionAffected if The installed product is Adobe Reader or Acrobat
-
Determine exact version numberNote the full version number displayed in the About dialog (for example, 9.4 or 10.1.0)Affected if The version displayed is any of the listed affected versions: 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 for version 9.x line
-
Compare version against affected rangesCheck if the installed version falls within: 9.x series before 9.5.5, 10.x series before 10.1.7, or 11.x series before 11.0.03Affected if The installed version is 9.0 through 9.4.x, any 10.x version before 10.1.7, or any 11.x version before 11.0.03
A user is affected if Adobe Reader or Acrobat version is 9.x before 9.5.5, 10.x before 10.1.7, or 11.x before 11.0.03, as these versions contain the memory corruption vulnerability.
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 9.5.5, 10.1.7, 11.0.03 or later. Given the CVSS 10 severity and code execution capability, prioritize patching all affected systems immediately.
Adobe Reader/Acrobat 9.5.5 (for 9.x), 10.1.7 (for 10.x), or 11.0.03 (for 11.x)
- 1. Identify the currently installed Adobe Reader or Adobe Acrobat version by opening the application and navigating to Help > About (or About Adobe Acrobat/Reader)
- 2. Navigate to the official Adobe security bulletin at http://www.adobe.com/support/security/bulletins/apsb13-15.html
- 3. Download the appropriate security update based on your current major version: For 9.x versions, download version 9.5.5 or later; For 10.x versions, download version 10.1.7 or later; For 11.x versions, download version 11.0.03 or later
- 4. Close all Adobe Reader/Acrobat instances and any applications that use PDF functionality
- 5. Run the downloaded installer and follow the on-screen prompts to apply the security update
- 6. Restart the system after installation completes
- 7. Verify the update was successful by checking the version in Help > About to confirm it matches or exceeds the fixed version for your branch
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-2725 — 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-2725 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