CVE-2024-30284
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 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 confidenceA Use After Free vulnerability in Adobe Acrobat Reader allows arbitrary code execution when a victim opens a specially crafted malicious PDF file. The vulnerability stems from improper memory management where the application attempts to access memory that has already been freed, potentially allowing an attacker to control execution flow.
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
- 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.
-
Locate Adobe Acrobat or Reader installationOn Windows, check for installation in typical paths such as C:\Program Files\Adobe\Acrobat DC\ or C:\Program Files (x86)\Adobe\Acrobat 20.0\. On macOS, check /Applications for Adobe Acrobat.app or Adobe Acrobat Reader.app.Affected if Adobe Acrobat or Reader software is present on the system
-
Identify the installed product and versionOn Windows, open the application and go to Help > About Adobe Acrobat DC/Reader, or check the Windows Registry under HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\Version or HKLM\SOFTWARE\Adobe\Acrobat Reader\DC\Version. On macOS, right-click the app in Applications and select Get Info to view the version.Affected if The installed version falls within the affected ranges: 15.007.20033 through 24.002.20758 (DC versions), or 20.001.30002 through 20.005.30634 (version 20.x)
-
Confirm the product edition typeDetermine whether the installed product is Acrobat/Reader DC (continuous track, version 24.x and 15.x) or Acrobat/Reader classic (version 20.x). DC versions have major version 24.x or 15.x, while classic versions have major version 20.x.Affected if The version matches the affected range for its respective track (DC or classic)
-
Verify PDF handling by AdobeCheck file association settings to confirm PDF files are configured to open with Adobe Acrobat or Reader by default. On Windows, go to Settings > Apps > Default Apps > Choose default apps by file type and verify .pdf association. On macOS, right-click a PDF file > Get Info > Open with.Affected if PDF files are set to open with an affected version of Adobe Acrobat or Reader
A user is affected if Adobe Acrobat or Reader is installed with a version between 15.007.20033 and 24.002.20758 (DC/Reader DC) or between 20.001.30002 and 20.005.30634 (classic 20.x), and PDF files are opened using that vulnerable application.
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 patched version (20.005.30575 or later for version 20.x, 24.002.20737 or later for version 24.x). Avoid opening PDF files from untrusted sources.
Acrobat DC/Reader DC: 24.002.20759 or later | Acrobat/Reader 2020: 20.005.30635 or later
- 1. Open Adobe Acrobat or Acrobat Reader on the affected system
- 2. Navigate to Help > Check for Updates (or use the automatic update feature)
- 3. Allow the update to download and install the fixed version
- 4. Alternatively, download the fixed version directly from helpx.adobe.com - for DC (Continuous) track: version 24.002.20759 or later; for 2020 track: version 20.005.30635 or later
- 5. Restart the application after the update completes
- 6. Verify the installed version matches or exceeds the fixed release numbers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30284 — 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-30284 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