dbcve.org
AcrobatApplication · Adobe

CVE-2024-41834

MEDIUM · 5.5 CVSS v3.1 Published 2024-08-14
Fix available
A fix is available. Upgrade to 20.005.30655 / 24.001.30159 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.30636, 24.002.20965, 24.002.20964, 24.001.30123 and earlier 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

An out-of-bounds read vulnerability exists in Adobe Acrobat Reader that allows reading beyond allocated memory buffers, potentially exposing sensitive memory contents. This information disclosure can be leveraged to bypass ASLR mitigation, aiding further exploitation. Successful attack requires victim interaction to open a malicious PDF file.

MitigationUpdate Adobe Acrobat Reader to the latest version beyond 24.002.20965 (or the latest available version) to obtain the security patch. Implement user training to avoid opening untrusted PDF files as an additional defensive layer.

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
AcrobatApplication
Affected:>= 20.001.30005, < 20.005.30655>= 24.001.20604, < 24.001.30159
Acrobat DcApplication
Affected:>= 15.008.20082, < 24.002.21005
Acrobat ReaderApplication
Affected:>= 20.001.3005, < 20.005.30655
Acrobat Reader DcApplication
Affected:>= 15.008.20082, < 24.002.21005

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 installed Adobe product
    Open Adobe Acrobat Reader or Adobe Acrobat, then navigate to Help > About Adobe Acrobat Reader (or Acrobat) to see the exact product name and version number displayed in the dialog box
    Affected if The product is Adobe Acrobat Reader or Adobe Acrobat (not a different PDF viewer)
  2. Determine product track
    On the About dialog, look at the version number format: versions starting with 20xxx or 24xxx indicate the Continuous track (e.g., 24.001.20604), while versions starting with 15xxx or 24.002xxxx indicate the Classic/DC track (e.g., 24.002.21005)
    Affected if The product is either Adobe Acrobat Reader DC, Adobe Acrobat DC, Adobe Acrobat Reader, or Adobe Acrobat - all four product lines are affected but on different version schedules
  3. Check Continuous track version (20.x branch)
    If the version starts with 20 (e.g., 20.001.30005 through 20.005.306xx), compare your exact version to the range >= 20.001.30005 and < 20.005.30655
    Affected if Your installed version is 20.001.30005 or higher but lower than 20.005.30655
  4. Check Continuous track version (24.x branch)
    If the version starts with 24.001 (e.g., 24.001.20604), compare your exact version to the range >= 24.001.20604 and < 24.001.30159
    Affected if Your installed version is 24.001.20604 or higher but lower than 24.001.30159
  5. Check Classic/DC track version
    If the version starts with 15 or 24.002 (e.g., 15.008.20082 or 24.002.21005), compare your exact version to the range >= 15.008.20082 and < 24.002.21005
    Affected if Your installed version is 15.008.20082 or higher but lower than 24.002.21005

You are affected if you are running any version of Adobe Acrobat Reader or Adobe Acrobat that falls within the vulnerable version ranges for your specific product track, and you open a malicious PDF file.

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.30655 / 24.001.30159 / 24.002.21005 or later
Fixed in 20.005.3065524.001.3015924.002.21005
Interim mitigation

Update Adobe Acrobat Reader to the latest version beyond 24.002.20965 (or the latest available version) to obtain the security patch. Implement user training to avoid opening untrusted PDF files as an additional defensive layer.

Recommended fix High confidence

Acrobat/Acrobat Reader: 20.005.30655 or later; 24.001.30159 or later; 24.002.21005 or later (for DC variants)

  1. Open Adobe Acrobat or Adobe Acrobat Reader
  2. Go to Help > Check for Updates (or Help > About Adobe Acrobat Reader)
  3. Allow the application to check for and install any available updates
  4. Alternatively, download the latest version from the official Adobe website: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
  5. Restart the application after updates complete
  6. Verify the version by going to Help > About to confirm you have a fixed version (20.005.30655 or later for 20.x releases; 24.001.30159 or later for 24.x releases; 24.002.21005 or later for DC variants)
Caveat Standard minor version upgrades typically have minimal breaking changes; however, always test critical workflows after updating PDF software in production environments

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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