CVE-2024-30280
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 read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 read vulnerability when parsing specially crafted PDF files. The vulnerability allows reading past the end of allocated memory structures, which could be leveraged by an attacker to achieve 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.
-
Verify Adobe Acrobat Reader is installedCheck for the presence of Adobe Acrobat Reader or Adobe Acrobat on the system. Common installation paths: C:\Program Files\Adobe\Adobe Acrobat <version>\Reader or C:\Program Files (x86)\Adobe\Acrobat Reader DC. On macOS, check /Applications for Adobe Acrobat or Adobe Acrobat Reader.Affected if Adobe Acrobat Reader or Adobe Acrobat is installed and the version falls within the affected ranges.
-
Determine the exact installed versionOpen Adobe Acrobat Reader, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). Alternatively, right-click the executable file (AcroRd32.exe or AcroRd64.exe for Reader, or AcroTray.exe) and select Properties, then view the Details tab for the Product Version.Affected if The version number displayed is less than 24.002.20759 for DC variants, or less than 20.005.30635/20.005.30636 for classic versions.
-
Confirm version matches DC or classic trackIdentify whether the installed product is Acrobat DC (continuous release) or Acrobat classic (20.x). DC versions are typically labeled as 'Acrobat Reader DC' or 'Acrobat DC' and have version numbers in the 24.x range. Classic versions are labeled as 'Acrobat Reader' or 'Acrobat' with version numbers in the 20.x range.Affected if The version number follows the DC pattern (15.x to 24.x) and is >= 15.007.20033 but < 24.002.20759, OR follows the classic pattern (20.x) and is >= 20.001.30002 but < 20.005.30635/20.005.30636.
-
Note that the vulnerability is triggered by parsing PDFsUnderstand that this is a file parsing vulnerability. The flaw is present in the PDF parsing engine and is triggered when opening a specially crafted PDF file.Affected if The vulnerable version of Adobe Acrobat Reader or Acrobat is installed, regardless of whether the user has opened a malicious PDF file.
The user is affected if Adobe Acrobat Reader or Adobe Acrobat is installed with a version number within the ranges: 15.007.20033 to 24.002.20758 (DC track) or 20.001.30002 to 20.005.30634/20.005.30635 (classic track).
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 versions newer than 24.002.20736 or 20.005.30574, and enforce user awareness to avoid opening untrusted PDF files.
Adobe Acrobat DC 24.002.20759 or later; Adobe Acrobat Reader DC 24.002.20759 or later; Adobe Acrobat (Classic) 20.005.30635 or later; Adobe Acrobat Reader (Classic) 20.005.30635 or later
- Close all Adobe Acrobat or Adobe Reader instances
- Download the latest version from the official Adobe website (get.adobe.com/reader for Reader, or directly from Adobe for Acrobat)
- Run the installer and follow the prompts to complete the installation
- Restart your computer if prompted
- Verify the installed version by opening Adobe Reader/Acrobat and checking Help > About
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-30280 — 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-30280 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