CVE-2024-49530
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 a Use After Free 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 a Use After Free vulnerability where the application continues using a memory pointer after it has been freed, potentially allowing arbitrary code execution. Successful exploitation requires a victim to open a malicious PDF file, and the attack executes 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< 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
- 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.
-
Locate installed Adobe Acrobat or Reader executableOn Windows, check C:\Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe or C:\Program Files (x86)\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe. On macOS, check /Applications/Adobe Acrobat Reader DC.app or /Applications/Adobe Acrobat.app.Affected if Adobe Acrobat or Reader software is present on the system
-
Identify exact product variantCheck the product name in the executable's file properties (right-click > Properties > Details) or the folder name where the executable resides to determine if it is Adobe Acrobat versus Adobe Acrobat Reader, and whether it is the DC (Document Cloud) version.Affected if The product is Adobe Acrobat Reader, Adobe Acrobat Reader Dc, Adobe Acrobat Dc, or Adobe Acrobat (all variants are affected)
-
Determine installed version numberRight-click the Acrobat.exe or AcroRd32.exe file, select Properties, go to the Details tab, and note the Product Version or File Version field. Alternatively, open the application and go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).Affected if Version cannot be determined (version check cannot be completed)
-
Compare against affected versionsMatch your installed version number against these vulnerable ranges: Acrobat Reader < 20.005.30748 OR < 24.005.20320 (Dc); Acrobat < 20.005.30748 OR >= 24.0.0 AND < 24.001.30225 OR < 24.005.20320 (Dc). Version format may appear as e.g., 24.001.30206 or 20.005.30733.Affected if Installed version falls within any of the affected version ranges listed
A user is affected if Adobe Acrobat Reader or Acrobat is installed with a version number below 20.005.30748, below 24.005.20320 (for DC variants), or between 24.0.0 and 24.001.30224 (for non-DC Acrobat).
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 version beyond the affected releases (24.005.20307, 24.001.30213, 24.001.30193, 20.005.30730, 20.005.30710 and earlier). Until patched, avoid opening untrusted or unexpected PDF files from unknown sources.
Adobe Acrobat/Reader 20.005.30748 (Classic) or 24.005.20320/24.001.30225 (DC) depending on product variant
- 1. Identify the installed Adobe Acrobat or Adobe Acrobat Reader version by navigating to Help > About (or on Mac, Acrobat/Reader > About Adobe Acrobat/Reader)
- 2. For Acrobat Classic (version 20.x): upgrade to version 20.005.30748 or later
- 3. For Acrobat/Acrobat Reader DC (version 24.x): upgrade to the appropriate fixed version - Acrobat DC to 24.005.20320 or later, or version 24.001.30225 or later for the continuous track
- 4. Download the fixed version from the official Adobe website at get.adobe.com/reader or get.adobe.com/acrobat
- 5. Close all instances of Adobe Acrobat/Reader before running the installer
- 6. Run the installer and follow the prompts to complete the upgrade
- 7. Restart the application after installation completes
- 8. Verify the version by checking Help > About to confirm the installed version matches or exceeds the fixed release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA0.5 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-49530 — 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-49530 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