CVE-2024-30310
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 an out-of-bounds write 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 an out-of-bounds write vulnerability allowing arbitrary code execution when a user opens a malicious PDF file. The vulnerability stems from improper bounds checking in the PDF rendering engine, enabling memory corruption that can be leveraged for code execution in the context of the current user.
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.
-
Check if Adobe Acrobat or Reader is installedOn Windows, open Programs and Features or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, DisplayVersion' in PowerShell. On macOS, check /Applications for Acrobat or Reader apps.Affected if Either Adobe Acrobat or Adobe Acrobat Reader is present on the system
-
Identify the exact product versionRight-click the Adobe Acrobat/Reader application in Programs and Features (Windows) or right-click the app in /Applications and select Get Info (macOS). The version is typically displayed as DisplayVersion or Version. Alternatively, open the application and go to Help > About Adobe Acrobat Reader.Affected if Version cannot be determined or does not match the expected version format
-
Compare your version against affected rangesMatch your installed version to the following ranges: Acrobat/Reader DC continuous: 15.007.20033 through 24.002.20758 (fix is 24.002.20759+); Acrobat/Reader 20.x classic: 20.001.30002 through 20.005.30634 (fix is 20.005.30635+ for Reader, 20.005.30636+ for Acrobat).Affected if Installed version falls within any of the affected ranges listed
-
Verify PDF files can be openedConfirm that the PDF rendering engine is functional by opening any PDF file in the installed Adobe product.Affected if PDF functionality is available and a malicious file could be processed
If Adobe Acrobat or Reader is installed and the version falls within 15.007.20033 to 24.002.20758 (DC) or 20.001.30002 to 20.005.30634 (20.x), the environment is vulnerable when processing untrusted PDF files.
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.005.30575 or later for 20.x, 24.002.20737 or later for 24.x) to remediate the vulnerability. Avoid opening untrusted PDF files until updates are applied.
Acrobat DC/Reader DC: upgrade to 24.002.20759 or later; Acrobat/Reader Classic (2020): upgrade to 20.005.30635 or later
- 1. Open Adobe Acrobat or Acrobat Reader
- 2. Navigate to Help > About Adobe Acrobat (or About Adobe Reader) to check the current version
- 3. If the installed version is less than 24.002.20759 (for Continuous track) or less than 20.005.30635/20.005.30636 (for Classic track), download the latest version from the official Adobe website
- 4. Run the installer and follow the prompts to complete the upgrade
- 5. Verify the version after installation matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-30310 — 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-30310 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