CVE-2024-49532
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 where parsing a specially crafted PDF file allows reading memory beyond allocated buffers. This information disclosure can leak sensitive memory contents and potentially bypass ASLR mitigation, creating potential for chaining with code execution exploits.
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.
-
Check Adobe Acrobat Reader version via Help menuOpen Adobe Acrobat Reader, then go to Help > About Adobe Acrobat Reader. Note the version number displayed in the dialog.Affected if The version shown is earlier than 20.005.30748, or falls between 24.0.0.0 and 24.001.30224 (for standard Acrobat) or is earlier than 24.005.20320 (for Acrobat Reader Dc).
-
Check version via command line or scriptUse the command: 'reg query "HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-1033-7B44-A95000000001}" /v DisplayVersion' for 32-bit Reader, or adjust the registry path for 64-bit (replace with {AC76BA86-7AD7-1033-7B44-A95000000000}).Affected if The returned DisplayVersion value is less than 20.005.30748, or is 24.x less than 24.001.30225 (for Acrobat) or less than 24.005.20320 (for Reader Dc).
-
Identify the exact product variantCheck if the installed product is Adobe Acrobat (standard), Adobe Acrobat Dc, Adobe Acrobat Reader, or Adobe Acrobat Reader Dc. This determines which version threshold applies. Look at the product name in the About dialog or the registry Uninstall key (ProductName value).Affected if The product is Adobe Acrobat Reader Dc and the version is below 24.005.20320, or Adobe Acrobat Reader (non-Dc) below 20.005.30748, or Adobe Acrobat Dc below 24.005.20320, or Adobe Acrobat (non-Dc) below 20.005.30748 or between 24.0 and 24.001.30224.
-
Confirm PDF parsing is enabledThis vulnerability is triggered when parsing a specially crafted PDF file. Verify that PDF handling features are active by opening any PDF in the application. The vulnerability exists in the core PDF parsing engine regardless of specific settings.Affected if PDF files can be opened and parsed by the application. The vulnerable code path is exercised during normal PDF document processing.
You are affected if the installed Adobe Acrobat Reader or Acrobat Dc version is lower than 20.005.30748 (for version 20.x), lower than 24.001.30225 (for Acrobat version 24.x), or lower than 24.005.20320 (for Reader Dc or Acrobat Dc version 24.x).
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 (24.005.20360 or later for version 24.x, 20.005.30745 or later for version 20.x). Ensure patch management processes address client-side applications.
Adobe Acrobat/Reader 20.005.30748+ (20.x line), 24.001.30225+ (24.0.x line), or 24.005.20320+ (Dc line) depending on your product branch
- 1. Identify the currently installed Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat)
- 2. Determine which product line and version branch you are using (20.x, 24.0.x, 24.5.x, or Dc variants)
- 3. For Acrobat/Acrobat Reader 20.x users: Upgrade to version 20.005.30748 or later
- 4. For Acrobat/Acrobat Reader 24.0.x users: Upgrade to version 24.001.30225 or later
- 5. For Acrobat Dc/Acrobat Reader Dc users: Upgrade to version 24.005.20320 or later
- 6. Download the latest version from the official Adobe website (helpx.adobe.com) or use Adobe's automatic update feature
- 7. Restart the application after installation
- 8. Verify the version has been updated by checking Help > About again
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49532 — 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-49532 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