CVE-2024-34100
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 confidenceAdobe Acrobat Reader contains a Use After Free (UAF) vulnerability where memory is accessed after being freed, allowing arbitrary code execution. The vulnerability affects versions 20.005.30574, 24.002.20736 and earlier, and requires a victim to open a 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>= 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.
-
Identify installed Adobe productOpen Adobe Acrobat Reader or Adobe Acrobat, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Alternatively, on Windows, right-click the executable in Program Files and select Properties > Details to view the version. On Mac, click the application name in the menu bar and select About.Affected if The installed software is Adobe Acrobat Reader Dc, Adobe Acrobat Dc, Adobe Acrobat Reader, or Adobe Acrobat.
-
Check Adobe Acrobat Reader Dc version on WindowsNavigate to C:\Program Files\Adobe\Acrobat DC\Acrobat\ and right-click AcroRd32.exe (Reader) or AcroTray.exe (Acrobat). Select Properties, then look at the File Version in the Details tab.Affected if Version is 15.007.20033 or higher but below 24.002.20759.
-
Check Adobe Acrobat Reader version on MacOpen Finder, navigate to /Applications/Adobe Acrobat Reader DC.app, right-click and select Show Package Contents. Open Contents/Info.plist and look for CFBundleShortVersionString or CFBundleVersion.Affected if Version is 15.007.20033 or higher but below 24.002.20759.
-
Check Adobe Acrobat (legacy) versionOpen the application and go to Help > About Adobe Acrobat, or on Windows check the executable properties at C:\Program Files\Adobe\Acrobat\Acrobat\Acrobat.exe for version details.Affected if Version is 20.001.30002 or higher but below 20.005.30635 (or below 20.005.30636 depending on platform).
-
Verify JavaScript is enabled in Reader settings (prerequisite for exploitation)In Adobe Acrobat Reader, go to Edit > Preferences > JavaScript. Check if 'Enable Adobe JavaScript' is checked. This setting must be enabled for the vulnerability to be exploitable.Affected if JavaScript is enabled in the application settings.
You are affected if you have Adobe Acrobat Reader Dc, Adobe Acrobat Dc, Adobe Acrobat, or Adobe Acrobat Reader installed with a version matching the affected ranges (15.007.20033 to 24.002.20759 for DC versions, or 20.001.30002 to 20.005.30635/20.005.30636 for legacy versions) and JavaScript is enabled.
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 provided by Adobe. Until patched, avoid opening untrusted PDF files and disable JavaScript in Reader settings.
Adobe Acrobat/Reader DC version 24.002.20759 or later (Continuous track); Adobe Acrobat/Reader version 20.005.30635/20.005.30636 or later (Classic track)
- 1. Open Adobe Acrobat or Adobe Reader on the affected system
- 2. Navigate to Help > Check for Updates (or use the Help menu)
- 3. Allow the application to check for and install the latest updates
- 4. Alternatively, download the latest version from the official Adobe website: https://get.adobe.com/reader/ or https://get.adobe.com/acrobat/
- 5. Verify the version by going to Help > About Adobe Acrobat/Reader
- 6. Confirm the installed version is 24.002.20759 or later for DC versions, or 20.005.30635/20.005.30636 or later for Classic versions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34100 — 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-34100 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