dbcve.org
Acrobat DcApplication · Adobe

CVE-2024-34101

MEDIUM · 5.5 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 →
58/100
Remediation priority · Elevated
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 Answer: are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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

Adobe Acrobat Reader contains an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. An attacker can exploit this by crafting a malicious PDF file that, when opened by a victim, triggers the vulnerability and could potentially bypass ASLR as a secondary impact.

MitigationUpdate Adobe Acrobat Reader to a version newer than 20.005.30574 or 24.002.20736, and educate users to avoid opening untrusted PDF files.

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
None
Availability
None

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N

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 if Adobe Acrobat or Reader is installed
    On Windows, check registry key HKLM\SOFTWARE\Adobe\Acrobat Reader\ or HKLM\SOFTWARE\Adobe\Acrobat\ for installed entries. On macOS, check /Applications for Adobe Acrobat Reader.app or Adobe Acrobat.app
    Affected if No Adobe Acrobat or Reader installation is found, then the system is not directly affected by this vulnerability through this application.
  2. Determine the exact version of Adobe Acrobat Reader
    On Windows, open the Adobe Acrobat Reader executable (AcroRd32.exe) properties and view the File Version, or query the registry at HKLM\SOFTWARE\Adobe\Acrobat Reader\DC\Install\InstallPath. On macOS, right-click the application and select Get Info to view the version.
    Affected if Unable to determine the installed version, making it unclear whether the installation falls within the affected ranges.
  3. Compare the installed version against affected ranges
    For Continuous (DC) track versions: check if version is >= 15.007.20033 AND < 24.002.20759. For 2020 track versions: check if version is >= 20.001.30002 AND < 20.005.30635 (or < 20.005.30636 depending on product). Match the track to your installation (Acrobat/Reader DC uses continuous; Acrobat/Reader 2020 uses the 20.xx version numbers).
    Affected if The installed version falls within any of the affected ranges: 15.007.20033 through 24.002.20758 (DC track), or 20.001.30002 through 20.005.30634 (2020 track).
  4. Verify the PDF handling component is in use
    The vulnerability is triggered when a user opens a maliciously crafted PDF file in Adobe Acrobat Reader. Check if the application is configured as the default PDF handler or frequently used for opening PDF documents.
    Affected if Adobe Acrobat Reader is the default PDF viewer or is regularly used to open PDF files from untrusted sources.

If Adobe Acrobat Reader or Adobe Acrobat is installed and its version falls within the affected ranges (15.007.20033 to 24.002.20758 for DC track, or 20.001.30002 to 20.005.30634 for 2020 track), the environment is potentially affected by this out-of-bounds read vulnerability when opening PDF files.

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 a version newer than 20.005.30574 or 24.002.20736, and educate users to avoid opening untrusted PDF files.

Recommended fix High confidence

24.002.20759 for Continuous track; 20.005.30635 or later for 2020 track

  1. 1. Identify the Adobe Acrobat product and version currently installed (Help > About Adobe Acrobat/Reader)
  2. 2. For Continuous track (Dc) versions: Upgrade to version 24.002.20759 or later
  3. 3. For 2020 track versions: Upgrade to version 20.005.30635 or later (or 20.005.30636 depending on specific product variant)
  4. 4. Download the update from the official Adobe website or use the application's built-in update mechanism (Help > Check for Updates)
  5. 5. Verify the installation after updating and confirm the version matches the fixed release
Caveat Standard Adobe update - verify compatibility with any third-party plugins or workflows before deploying enterprise-wide

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

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-34101 — 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-34101 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