CVE-2024-39383
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.30636, 24.002.20965, 24.002.20964, 24.001.30123 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 exploits memory that has been freed but still referenced, 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>= 20.001.3005, < 20.005.30655>= 24.001.20604, < 24.001.30159>= 24.002.20964, < 24.002.21005>= 20.001.3005, < 20.005.30655>= 24.002.20964, < 24.002.21005CVSS 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.
-
Check if Adobe Acrobat Reader is installedOn Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\Reader\DC\Install or check in Programs and Features. On macOS, check /Applications for Adobe Acrobat Reader.app.Affected if Adobe Acrobat Reader or Adobe Acrobat Reader Dc is installed on the system
-
Determine the installed version on WindowsOpen Registry Editor and go to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\Reader\DC\Install, then look for the Version value. Alternatively, open Adobe Acrobat Reader, go to Help > About Adobe Acrobat Reader.Affected if The version displayed is in the affected ranges: 20.001.3005 to 20.005.30655 (inclusive), or 24.002.20964 to 24.002.21004 (inclusive) for Reader Dc
-
Determine the installed version on macOSRight-click on Adobe Acrobat Reader.app in /Applications, select Get Info, and look at the Version field under General.Affected if The version displayed falls within the affected ranges listed above
-
Verify if Acrobat (not Reader) is installedCheck for Adobe Acrobat (not Reader) installation using the same methods, looking at the version in the same registry locations or via Help > About.Affected if Adobe Acrobat or Adobe Acrobat Dc is installed with a version in the ranges: 20.001.3005 to 20.005.30655, 24.001.20604 to 24.001.30158, or 24.002.20964 to 24.002.21004
You are affected if Adobe Acrobat Reader, Adobe Acrobat Reader Dc, Adobe Acrobat, or Adobe Acrobat Dc is installed with a version matching any of the listed affected ranges.
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.3065524.001.3015924.002.21005
Update Adobe Acrobat Reader to the latest patched version and exercise caution when opening PDF files from untrusted sources.
Adobe Acrobat/Reader 20.005.30655 or later; Acrobat 24.001.30159 or later; Acrobat/Reader DC 24.002.21005 or later
- Check current Adobe Acrobat/Reader version by opening the application, going to Help > About Adobe Acrobat (or Reader)
- Download the latest version of Adobe Acrobat or Adobe Reader from the official Adobe website (get.adobe.com/reader for Reader, or adobe.com for Acrobat)
- Close all instances of Adobe Acrobat or Reader
- Install the updated version by running the downloaded installer
- Restart the application and verify the version matches or exceeds the fixed release (20.005.30655 for version 20.x, 24.001.30159 for Acrobat 24.x, or 24.002.21005 for Acrobat/Reader DC 24.x)
- Ensure automatic updates are enabled to receive future security patches
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-39383 — 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-39383 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