dbcve.org
Acrobat DcApplication · Adobe

CVE-2024-30312

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

Out-of-bounds read vulnerability in Adobe Acrobat Reader allows reading memory beyond allocated buffers, potentially exposing sensitive memory contents including addresses that can be used to bypass ASLR mitigation. Exploitation requires a victim to open a malicious PDF or other supported file format.

MitigationUpdate Adobe Acrobat Reader to the latest patched version (beyond 24.002.20736 and 20.005.30574). Until patched, instruct users to avoid opening files from untrusted 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
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. Check Adobe Acrobat Reader version on Windows
    Open Adobe Acrobat Reader, then go to Help > About Adobe Acrobat Reader. Note the exact version number shown in the dialog.
    Affected if The version is >= 15.007.20033 and < 24.002.20759 for Acrobat Reader DC, or >= 20.001.30002 and < 20.005.30635 (or < 20.005.30636 depending on track)
  2. Check Adobe Acrobat version on Windows
    Open Adobe Acrobat (not Reader), then go to Help > About Adobe Acrobat. Note the exact version number shown in the dialog.
    Affected if The version is >= 15.007.20033 and < 24.002.20759 for Acrobat DC, or >= 20.001.30002 and < 20.005.30635 (or < 20.005.30636 depending on track)
  3. Check version via Windows Registry
    Open Registry Editor and navigate to HKLM\SOFTWARE\Adobe\Acrobat Reader\<version> or HKLM\SOFTWARE\Adobe\Acrobat\<version> (under the relevant installed version key), then look at the 'Version' value in the right pane.
    Affected if The registry Version value falls within any of the affected version ranges listed in the CVE
  4. Check version on macOS
    Open Finder, navigate to Applications, right-click Adobe Acrobat Reader or Adobe Acrobat, select Get Info, and note the Version number displayed.
    Affected if The displayed version falls within any of the affected version ranges
  5. Verify file handling configuration
    In Adobe Acrobat/Reader, go to Edit > Preferences > Security (or Privacy) and review settings related to automatically opening PDF files or enabling JavaScript for PDF documents.
    Affected if Automatic file opening or JavaScript is enabled, which increases the attack surface for this vulnerability that triggers upon opening malicious files

A user is affected if Adobe Acrobat or Adobe Acrobat Reader is installed with a version number matching any of the affected ranges (>= 15.007.20033, < 24.002.20759, or >= 20.001.30002, < 20.005.30635/20.005.30636) and the user opens files from untrusted sources.

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 and 20.005.30574). Until patched, instruct users to avoid opening files from untrusted sources.

Recommended fix High confidence

Acrobat Dc/Reader Dc (Continuous): 24.002.20759 or later | Acrobat/Acrobat Reader (Classic): 20.005.30635/20.005.30636 or later

  1. 1. Identify which track/version of Adobe Acrobat or Acrobat Reader is installed (Continuous vs Classic)
  2. 2. For Continuous track (versions 15.x-24.x): Download and install version 24.002.20759 or later from the official Adobe website
  3. 3. For Classic track (versions 20.x): Download and install version 20.005.30635 (Acrobat) or 20.005.30636 (Acrobat Reader) or later from the official Adobe website
  4. 4. Verify the installation by checking Help > About Adobe Acrobat/Reader to confirm the version number
  5. 5. Ensure user interaction is minimized - warn users not to open untrusted PDF files
Caveat Standard upgrade - no major breaking changes expected for security updates

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
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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