CVE-2024-30311
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 · uneditedAcrobat Reader versions 20.005.30574, 24.002.20736 and earlier Answer: are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
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 Acrobat Reader contains an out-of-bounds read vulnerability allowing disclosure of sensitive memory. An attacker could exploit this by crafting a malicious PDF file that, when opened by a victim, reads beyond allocated memory boundaries. This information disclosure can be leveraged to defeat ASLR mitigations, potentially facilitating further exploitation.
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>= 15.007.20033, < 24.002.20759>= 15.007.20033, < 24.002.20759>= 20.001.30002, < 20.005.30635>= 20.001.30002, < 20.005.30636>= 20.001.30002, < 20.005.30635>= 20.001.30002, < 20.005.30636CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 if Adobe Acrobat Reader is installedOpen Adobe Acrobat Reader and go to Help > About Adobe Acrobat Reader, or right-click the Adobe Acrobat Reader icon and select Properties to view version informationAffected if Adobe Acrobat Reader or Adobe Acrobat DC is present on the system
-
Identify the product branch and exact version numberLocate the full version number displayed in the About dialog (for example, 20.005.30635 or 24.002.20759). Note whether it is a 20.x (classic) or 24.x (continuous) releaseAffected if The exact version is displayed and can be compared against ranges
-
Determine if the installed version falls within an affected rangeCompare your installed version against: 20.x branch: 20.001.30002 up to (but not including) 20.005.30635; 24.x branch: 15.007.20033 up to (but not including) 24.002.20759. For version 20.x, versions 20.005.30635 and later are fixed. For version 24.x, versions 24.002.20759 and later are fixedAffected if Installed version is greater than or equal to 20.001.30002 but less than 20.005.30635, OR greater than or equal to 15.007.20033 but less than 24.002.20759
-
Verify the product type matches affected variantsConfirm whether the installed product is Adobe Acrobat Reader DC, Adobe Acrobat DC, Adobe Acrobat (classic), or Adobe Acrobat Reader (classic). The vulnerability affects all these variants within the version rangesAffected if The product is any variant of Adobe Acrobat or Adobe Acrobat Reader within the affected version ranges
If Adobe Acrobat Reader or Adobe Acrobat is installed with a version that falls within the affected ranges (20.001.30002 to 20.005.30634 for 20.x, or 15.007.20033 to 24.002.20758 for 24.x), the environment is vulnerable to this out-of-bounds read flaw.
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 · scoped20.005.3063520.005.3063624.002.20759
Update Adobe Acrobat Reader to the latest version (20.005.30575 or later for the 20.x branch, 24.002.20737 or later for the 24.x branch) and enforce policies restricting opening of untrusted PDF files from unknown sources.
Adobe Acrobat DC/Reader DC 24.002.20759 or later; Adobe Acrobat/Reader 20.x (Classic) 20.005.30635 or later
- 1. Open Adobe Acrobat or Adobe Reader
- 2. Navigate to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to check the current version
- 3. If the installed version is below 24.002.20759 (for Continuous track) or below 20.005.30635/20.005.30636 (for Classic track), proceed with the upgrade
- 4. Download the latest version from the official Adobe website: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 5. Run the installer and follow the prompts to complete the upgrade
- 6. After installation, verify the version by checking Help > About again to confirm the version is 24.002.20759 or later for DC, or 20.005.30635/20.005.30636 or later for version 20.x
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30311 — 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-2024-30311 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