CVE-2024-34096
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 vulnerability where memory is accessed after it has been freed, potentially allowing arbitrary code execution. Successful 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>= 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.
-
Verify Adobe Acrobat or Reader is installedOn Windows, open Control Panel > Programs and Features and look for 'Adobe Acrobat' or 'Adobe Acrobat Reader'. On macOS, check the /Applications folder for these applications.Affected if Neither Adobe Acrobat nor Adobe Acrobat Reader is installed on the system
-
Identify the installed product variant and version numberOpen the application, then go to Help > About Adobe Acrobat (or Reader). The version number will be displayed in the format such as 24.x.x.xx or 20.x.x.xx. Record this exact version number.Affected if The application is installed but you cannot determine the exact version number
-
Compare Classic version (20.x) against affected rangeIf the version starts with 20, check if it is less than 20.005.30635. Versions 20.001.30002 through 20.005.30634 are affected.Affected if Installed version is 20.001.30002 or higher but below 20.005.30635
-
Compare 2024 version (24.x) against affected rangeIf the version starts with 24, check if it is less than 24.002.20759. Versions 24.002.20758 and below are affected.Affected if Installed version is 15.007.20033 or higher but below 24.002.20759
-
Confirm whether PDF files from untrusted sources are openedThis vulnerability requires user interaction: the victim must open a specially crafted malicious PDF file. Check whether users in your environment commonly open PDF attachments or files from untrusted sources.Affected if Users open PDF files from untrusted or unknown sources, and the installed version falls within the affected ranges
If Adobe Acrobat or Reader is installed with a version >= 15.007.20033 but < 24.002.20759 (for 24.x) or >= 20.001.30002 but < 20.005.30635 (for 20.x), and users may open untrusted PDF files, the environment is potentially affected.
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.006.00120 or later for 20.x, 24.006.00178 or later for 24.x) and exercise caution when opening PDF files from untrusted sources.
Acrobat DC/Acrobat Reader DC: upgrade to version 24.002.20759 or later | Acrobat Classic 2020/Acrobat Reader Classic 2020: upgrade to version 20.005.30635 or later
- 1. Open Adobe Acrobat or Adobe Acrobat Reader on your system
- 2. Navigate to Help > Check for Updates or use the Help menu to check for available updates
- 3. Download and install the latest available version from Adobe's official website if automatic update doesn't initiate
- 4. Alternatively, download directly from Adobe's official Acrobat DC or Acrobat classic pages: https://get.adobe.com/reader/ or https://www.adobe.com/acrobat.html
- 5. Restart the application after installation completes
- 6. Verify the installed version by going to Help > About Adobe Acrobat [Reader] to confirm version 24.002.20759 (or later for DC) or 20.005.30635 (or later for classic 20.x) is installed
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-34096 — 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-34096 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