dbcve.org
Acrobat DcApplication · Adobe

CVE-2024-34094

HIGH · 7.8 CVSS v3.1 Published 2024-05-15
Fix available
A fix is available. Upgrade to 20.005.30635 / 20.005.30636 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Acrobat 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 confidence

This is a Use After Free vulnerability in Adobe Acrobat Reader that allows an attacker to achieve arbitrary code execution by tricking a victim into opening a specially crafted malicious PDF file. The vulnerability exploits memory management flaws in the software, and successful exploitation occurs within the security context of the currently logged-on user.

MitigationUpdate Adobe Acrobat Reader to the latest patched version beyond 24.002.20736 (for version 24) and beyond 20.005.30574 (for version 20). Additionally, educate users to avoid opening PDF files from untrusted or unknown sources.

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
Acrobat DcApplication
Affected:>= 15.007.20033, < 24.002.20759
Acrobat Reader DcApplication
Affected:>= 15.007.20033, < 24.002.20759
AcrobatApplication
Affected:>= 20.001.30002, < 20.005.30635>= 20.001.30002, < 20.005.30636
Acrobat ReaderApplication
Affected:>= 20.001.30002, < 20.005.30635>= 20.001.30002, < 20.005.30636

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Adobe product
    Open Adobe Acrobat Reader or Adobe Acrobat, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Note the product name displayed (Acrobat Reader Dc, Acrobat Dc, Acrobat, or Acrobat Reader).
    Affected if The product is Adobe Acrobat Reader or Adobe Acrobat (any variant).
  2. Check the product version number
    In the About dialog window, locate the version number displayed (for example, 24.001.20604 or 20.005.30579). Record this full version string exactly as shown.
    Affected if A version number is present and can be compared against the affected ranges.
  3. Compare version 24.x builds against affected range
    If your version begins with 24.x (for example, 24.001.20604), verify if it falls within >= 15.007.20033 AND < 24.002.20759. Check the fourth segment (20759 is the upper bound).
    Affected if Version is 24.x and is less than 24.002.20759.
  4. Compare version 20.x builds against affected range
    If your version begins with 20.x (for example, 20.005.30579), verify if it falls within >= 20.001.30002 AND < 20.005.30635 (or 20.005.30636 depending on product). Check the fourth segment (30635/30636 is the upper bound).
    Affected if Version is 20.x and is less than 20.005.30635 or 20.005.30636.
  5. Confirm the product edition (Continuous vs Classic)
    In the About dialog, look for 'Continuous' or 'Classic' in the version description. Continuous releases use the 24.x numbering, while Classic releases use 20.x numbering. This helps map your version to the correct affected range.
    Affected if The product is a Continuous (24.x) or Classic (20.x) edition that falls within the affected version ranges.

A user is affected if they have Adobe Acrobat Reader or Adobe Acrobat installed with version 24.x below 24.002.20759, or version 20.x below 20.005.30635/30636, matching the 15.007.20033 minimum threshold.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 20.005.30635 / 20.005.30636 / 24.002.20759 or later
Fixed in 20.005.3063520.005.3063624.002.20759
Interim mitigation

Update Adobe Acrobat Reader to the latest patched version beyond 24.002.20736 (for version 24) and beyond 20.005.30574 (for version 20). Additionally, educate users to avoid opening PDF files from untrusted or unknown sources.

Recommended fix High confidence

Adobe Acrobat DC 24.002.20759+ / 20.005.30635+ or Acrobat Reader DC 24.002.20759+ / 20.005.30635+

  1. 1. Close all instances of Adobe Acrobat or Acrobat Reader running on the system
  2. 2. Navigate to the official Adobe support page at helpx.adobe.com or the Adobe Acrobat download page
  3. 3. Download the appropriate version of Adobe Acrobat DC or Acrobat Reader DC for your installed version (Continuous or Standard track)
  4. 4. For Acrobat DC: Download version 24.002.20759 or later for the Continuous track, or version 20.005.30635 or later for the Standard track
  5. 5. For Acrobat Reader DC: Download version 24.002.20759 or later for the Continuous track, or version 20.005.30635 or later for the Standard track
  6. 6. Run the installer and follow the on-screen prompts to complete the installation
  7. 7. After installation, restart any Adobe applications and verify the version by going to Help > About Adobe Acrobat/Reader
Caveat Standard Adobe security update - no major breaking changes expected; ensure you back up any custom settings or preferences if needed

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-34094 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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