CVE-2013-2724
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 · uneditedStack-based buffer overflow in Adobe Reader and Acrobat 9.x before 9.5.5, 10.x before 10.1.7, and 11.x before 11.0.03 allows attackers to execute arbitrary code via unspecified vectors.
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 confidenceStack-based buffer overflow in Adobe Reader and Acrobat allows remote attackers to execute arbitrary code. The vulnerability affects versions 9.x before 9.5.5, 10.x before 10.1.7, and 11.x before 11.0.03.
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 Reader or Acrobat installationCheck for AcroRd32.exe (Reader) or Acro32.exe/Acrobat.exe (Acrobat) in typical installation paths such as C:\Program Files\Adobe\Adobe Reader X\ or C:\Program Files\Adobe\Adobe Acrobat X\, or query installed programs via registry or system inventory toolsAffected if Either Adobe Reader or Adobe Acrobat is present on the system
-
Locate the installed executable versionRight-click the Adobe executable (AcroRd32.exe for Reader, Acro32.exe or Acrobat.exe for Acrobat), select Properties, and view the Details tab for the Product Version field; alternatively, run 'wmic product where "name like 'Adobe%'" get name,version' in Command Prompt or use PowerShell Get-ItemProperty on the executableAffected if The executable version information is displayed
-
Extract the exact version numberRecord the full version number displayed in the Product Version field (for example, 9.4.0 or 10.1.6 or 11.0.02)Affected if A version number is obtained from the executable or installation
-
Compare version against affected rangesCheck if the installed version falls within these ranges: 9.x versions before 9.5.5, 10.x versions before 10.1.7, or 11.x versions before 11.0.03; for example, version 9.4 is affected because it is 9.x before 9.5.5, version 10.1.6 is affected because it is 10.x before 10.1.7, and version 11.0.02 is affected because it is 11.x before 11.0.03Affected if The installed version is 9.0 through 9.4.x, or 10.0 through 10.1.6, or 11.0.00 through 11.0.02
The system is affected if Adobe Reader or Acrobat is installed with a version in the 9.x series before 9.5.5, the 10.x series before 10.1.7, or the 11.x series before 11.0.03.
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 or later for 9.x, 10.1.7 or later for 10.x, and 11.0.03 or later for 11.x. Alternatively, disable or remove affected installations until patching is feasible.
Adobe Reader/Acrobat 9.5.5+ (for 9.x), 10.1.7+ (for 10.x), or 11.0.03+ (for 11.x)
- Check current Adobe Reader or Acrobat version by opening the application and navigating to Help > About Adobe Reader or Help > About Adobe Acrobat
- Note the exact version number (e.g., 9.1.2)
- Download the appropriate patched version from Adobe's official security bulletin at http://www.adobe.com/support/security/bulletins/apsb13-15.html
- For version 9.x: upgrade to Adobe Reader/Acrobat 9.5.5 or later
- For version 10.x: upgrade to Adobe Reader/Acrobat 10.1.7 or later
- For version 11.x: upgrade to Adobe Reader/Acrobat 11.0.03 or later
- Run the installer and follow the on-screen prompts to complete the installation
- Restart the application and verify the new version in Help > About
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-2724 — 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-2724 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