CVE-2024-49534
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 24.005.20307, 24.001.30213, 24.001.30193, 20.005.30730, 20.005.30710 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 confidenceAdobe Acrobat Reader contains an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents. An attacker could leverage this to potentially bypass security mitigations like ASLR by leaking memory addresses. Exploitation requires a victim to open a malicious PDF file.
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< 20.005.30748>= 24.0, < 24.001.30225< 24.005.20320< 20.005.30748< 24.005.20320CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe productOpen Adobe Acrobat or Reader, go to Help > About Adobe Acrobat Reader (or similar menu item) to see the exact product name and variant (such as Acrobat Reader DC, Acrobat DC, etc.)Affected if The installed product is Adobe Acrobat Reader or Adobe Acrobat of any variant
-
Determine installed version numberNote the full version number displayed in the About dialog. The version format typically appears as a sequence like XX.XXXX.XXXXX (e.g., 24.001.30225)Affected if The version number cannot be determined or is not visible
-
Compare version against affected rangesCheck if the installed version falls into any of these vulnerable ranges: Adobe Acrobat < 20.005.30748 OR >= 24.0 AND < 24.001.30225; Adobe Acrobat DC < 24.005.20320; Adobe Acrobat Reader < 20.005.30748; Adobe Acrobat Reader DC < 24.005.20320Affected if The installed version is lower than any of the listed thresholds for the matching product
-
Verify exploitation conditionRecall whether the system has been used to open PDF files from untrusted or unknown sources, as exploitation requires a victim to open a malicious PDFAffected if Users routinely open PDF files from untrusted sources and the product version is within the affected ranges
A user is affected if they have Adobe Acrobat Reader or Adobe Acrobat installed with a version below the patched thresholds AND they open PDF files, including from untrusted sources.
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.3074824.001.3022524.005.20320
Update Adobe Acrobat Reader to the latest patched version. Additionally, enforce policies restricting opening of untrusted or unexpected PDF files and educate users about the risks of opening files from untrusted sources.
Adobe Acrobat/Reader 20.005.30748 (20.x branch) or 24.001.30225/24.005.20320 (24.x branch) depending on product line
- 1. Identify the currently installed Adobe Acrobat or Reader version by opening the application, clicking Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. Based on your current version branch, download the appropriate fixed release:
- - For version 20.x users: Upgrade to Adobe Acrobat/Reader 20.005.30748 or later
- - For version 24.x standard users: Upgrade to Adobe Acrobat/Reader 24.001.30225 or later
- - For Acrobat Dc or Acrobat Reader Dc: Upgrade to version 24.005.20320 or later
- 3. Download the patched version from the official Adobe download center at get.adobe.com/reader or get.adobe.com/acrobat
- 4. Close all instances of Adobe Acrobat or Reader
- 5. Run the installer and follow the on-screen prompts to complete the upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49534 — 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-49534 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