CVE-2024-45107
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.30636, 24.002.20964, 24.001.30123, 24.002.20991 and earlier are affected by a Use After Free 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 confidenceA Use After Free vulnerability in Adobe Acrobat Reader allows an attacker to read sensitive memory contents after a memory region has been freed. This memory disclosure can be leveraged to defeat ASLR by leaking memory addresses. Exploitation requires a victim to open a specially crafted 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.001.30005, < 20.005.30655>= 24.001.20604, < 24.001.30159>= 15.007.20033, < 24.002.21005>= 20.001.30005, < 20.005.30655>= 15.007.20033, < 24.002.21005CVSS 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.
-
Verify Adobe Acrobat Reader is installedCheck the Windows registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\DC\InstallPath or look for the executable (AcroRd32.exe or AcroRd64.exe) in Program Files or Program Files (x86) directories.Affected if Adobe Acrobat Reader is present on the system.
-
Determine the installed versionOpen the executable properties of AcroRd32.exe or AcroRd64.exe and read the File Version field, or query the registry value at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\DC\InstallVersion.Affected if The version cannot be determined or the product is not found.
-
Compare version to affected rangesCompare the installed version against the following vulnerable ranges: 20.001.30005 through 20.005.30654, and 24.001.20604 through 24.001.30158. For Acrobat Reader DC, also compare to 15.007.20033 through 24.002.21004.Affected if The installed version falls within any of these ranges.
-
Confirm product type and buildIdentify whether the installation is Adobe Acrobat (Standard/Pro) or Adobe Acrobat Reader, and whether it includes DC (Document Cloud) by checking the registry path or executable name.Affected if The product matches Adobe Acrobat Reader Dc or Adobe Acrobat Reader with a vulnerable version.
-
Inspect recent PDF handling behaviorReview system activity logs or ask users if they have recently opened PDF files from untrusted or unknown sources, as exploitation requires opening a specially crafted malicious PDF.Affected if Users have opened untrusted PDF files while running a vulnerable version.
A user is affected if Adobe Acrobat Reader (or Reader DC) is installed with a version matching the ranges 20.001.30005-20.005.30654, 24.001.20604-24.001.30158, or 15.007.20033-24.002.21004.
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.3065524.001.3015924.002.21005
Update Adobe Acrobat Reader to the latest version beyond 24.002.20991. Additionally, enforce least-privilege execution and educate users to avoid opening PDF files from untrusted sources.
Acrobat 20.x: upgrade to 20.005.30655 or later | Acrobat 24.x: upgrade to 24.001.30159 or later | Acrobat DC/Reader DC: upgrade to 24.002.21005 or later
- 1. Open Adobe Acrobat or Acrobat Reader on the affected system
- 2. Navigate to Help > Check for Updates (or use the Help menu)
- 3. Download and install the latest version from get.adobe.com/acrobat or use the automatic update feature
- 4. Alternatively, download the specific fixed version directly from helpx.adobe.com
- 5. Verify the installed version by going to Help > About Adobe Acrobat (or Reader)
- 6. Confirm the version number matches or exceeds the fixed release: 20.005.30655, 24.001.30159, or 24.002.21005 depending on your product line
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45107 — 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-45107 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