CVE-2013-0624
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 bypass intended access restrictions via unspecified vectors, a different vulnerability than CVE-2013-0622.
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 confidenceAdobe Reader and Acrobat 9.x before 9.5.3, 10.x before 10.1.5, and 11.x before 11.0.1 contain an access restriction bypass vulnerability. Attackers can circumvent intended security controls via unspecified vectors, allowing unauthorized access or actions that should be restricted.
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 product is installedOpen Control Panel (Windows) or Applications folder (Mac) and look for Adobe Acrobat or Adobe Reader. Alternatively, search for 'AcroRd32.exe' (Reader) or 'Acrobat.exe' (Acrobat) in Program Files.Affected if Either Adobe Reader or Adobe Acrobat is present on the system
-
Locate the installed versionWindows: Right-click the Adobe icon, select Properties, and check the Version field in the Details tab. Or open the application, go to Help > About Adobe Reader/Acrobat. Mac: Right-click the application in Applications, select Get Info, and check the Version field.Affected if Unable to determine version because the product may be a different application or corrupted installation
-
Compare against affected versionsMatch your installed version number to the affected ranges: Adobe 9.x versions 9.0 through 9.4, Adobe 10.x versions 10.0 through 10.1.4, and Adobe 11.x version 11.0 are all affected.Affected if The installed version falls within 9.0-9.4, 10.0-10.1.4, or 11.0 (any 9.x before 9.5.3, 10.x before 10.1.5, or 11.x before 11.0.1)
-
Confirm product type and editionVerify whether the installed product is Adobe Reader (free) or Adobe Acrobat (commercial). Acrobat versions are listed as 'Acrobat X Pro', 'Acrobat X Standard', etc., while Reader versions display as 'Adobe Reader X' or similar.Affected if The product is Adobe Reader or Adobe Acrobat and the version matches the affected ranges
A system is affected if Adobe Reader or Adobe Acrobat is installed with any version from 9.0 through 9.4, 10.0 through 10.1.4, or 11.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 · scopedUpdate Adobe Reader and Acrobat to version 9.5.3, 10.1.5, or 11.0.1 or later. Given the CVSS 10 severity and access restriction bypass nature, prioritize patching across all affected systems immediately.
Adobe Reader/Acrobat 9.5.3 (or later 10.x/11.x versions: 10.1.5/11.0.1 respectively if upgrading to those branches)
- 1. Navigate to the Adobe Acrobat/Reader download page or the vendor security bulletin at http://www.adobe.com/support/security/bulletins/apsb13-02.html
- 2. Download the appropriate fixed version for your product: Adobe Reader 9.5.3 (for 9.x versions) or Adobe Acrobat 9.5.3
- 3. Close all running instances of Adobe Reader or Acrobat
- 4. Uninstall the current vulnerable version (9.0, 9.1, 9.1.1, or 9.1.2) from your system via Control Panel > Programs and Features
- 5. Install the downloaded fixed version (9.5.3)
- 6. Restart your computer if prompted
- 7. Verify the installed version matches the fixed release by opening Adobe Reader/Acrobat and checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.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,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-0624 — 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-0624 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