CVE-2024-30304
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.30539, 23.008.20470 and earlier are affected by a Use After Free vulnerability that could result in arbitrary code execution in the context of the current user. 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 a Use After Free vulnerability where memory is accessed after being freed, potentially allowing arbitrary code execution. Exploitation requires a victim to open a specially crafted malicious PDF file.
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>= 20.001.30002, < 20.005.30574>= 15.007.20033, < 23.008.20533>= 20.001.30002, < 20.005.30574>= 15.007.20033, < 23.008.20533CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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.
-
Verify Adobe Acrobat Reader is installedOn Windows, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\Acrobat Reader for the installation. On macOS, verify /Applications/Adobe Acrobat Reader exists.Affected if The software is not installed or no Reader product is found in the system.
-
Identify the installed Reader version and variantOpen Adobe Acrobat Reader, go to Help > About Adobe Acrobat Reader to display the version number. Note whether it is the standard Reader or Reader DC variant.Affected if No version information is displayed or the product is not Reader/Reader DC.
-
Compare version against affected rangesMatch the installed version to these ranges: 20.001.30002 through 20.005.30573 (for version 20.x releases), or 15.007.20033 through 23.008.20532 (for version 15.x/23.x releases). Versions below 20.001.30002 or at or above 20.005.30574 (for 20.x) and versions below 15.007.20033 or at or above 23.008.20533 (for 15.x/23.x) are NOT affected.Affected if The installed version falls within 20.001.30002 to 20.005.30573 inclusive, or within 15.007.20033 to 23.008.20532 inclusive.
You are affected if Adobe Acrobat Reader or Acrobat Reader DC is installed with a version matching the affected ranges, as the Use After Free vulnerability would trigger upon opening a malicious PDF file.
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.3057423.008.20533
Update Adobe Acrobat Reader to the latest version provided by Adobe. Avoid opening PDF files from untrusted sources.
Acrobat: 20.005.30574 or later (or latest 2024 release); Acrobat DC: 23.008.20533 or later (or latest 2024 release); Reader DC: 23.008.20533 or later (or latest 2024 release)
- 1. Close all Adobe Acrobat or Adobe Acrobat Reader instances that are currently running
- 2. Navigate to the official Adobe download page at https://get.adobe.com/reader/ or https://get.adobe.com/acrobat/
- 3. Download the latest version of Adobe Acrobat Reader DC or Adobe Acrobat DC for your operating system
- 4. Run the installer and follow the on-screen prompts to complete the installation
- 5. Alternatively, use the Adobe Creative Cloud desktop application to check for and apply available updates
- 6. After installation, verify the version by opening Adobe Acrobat/Reader and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat)
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-2024-30304 — 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-30304 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