CVE-2024-45112
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.002.21005, 24.001.30159, 20.005.30655, 24.003.20054 and earlier are affected by a Type Confusion vulnerability that could result in arbitrary code execution in the context of the current user. This issue occurs when a resource is accessed using a type that is not compatible with the actual object type, leading to a logic error that an attacker could exploit. 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 type confusion vulnerability where a resource is accessed using a type incompatible with the actual object type, leading to a logic error that can be exploited to achieve arbitrary code execution in the context of the current user. 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.005.30680>= 24.001.0, < 24.001.30187>= 24.003.0, < 24.003.20112< 20.005.30680>= 24.003.0, < 24.003.20112CVSS 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.
-
Identify if Adobe Acrobat/Reader is installedCheck your system for Adobe Acrobat or Adobe Acrobat Reader. On Windows, open Control Panel > Programs and Features, or run Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Select-Object DisplayName in PowerShell to list installed software.Affected if If neither Adobe Acrobat nor Adobe Acrobat Reader appears in the installed programs, the system is not affected.
-
Determine the installed version numberOpen the installed Adobe application, go to Help menu, and select About Adobe Acrobat (or About Adobe Acrobat Reader) to display the version number. Alternatively, on Windows check the registry key HKLM:\SOFTWARE\Adobe\Acrobat\DC\Version for Reader DC or Acrobat DC.Affected if If the version cannot be determined, the detection cannot be completed.
-
Compare version against affected rangesMatch your installed version against these vulnerable ranges: Adobe Acrobat (standalone) < 20.005.30680 OR >= 24.001.0 to < 24.001.30187; Adobe Acrobat DC >= 24.003.0 to < 24.003.20112; Adobe Acrobat Reader (standalone) < 20.005.30680; Adobe Acrobat Reader DC >= 24.003.0 to < 24.003.20112Affected if If the installed version falls within ANY of these ranges, the installation is affected by CVE-2024-45112.
Your environment is affected only if Adobe Acrobat or Adobe Acrobat Reader is installed AND its version matches one of the specified vulnerable ranges; otherwise, you are not affected by this CVE.
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.3068024.001.3018724.003.20112
Update Adobe Acrobat Reader to a patched version beyond 24.003.20054. Until patched, avoid opening PDF files from untrusted sources and disable JavaScript in Reader settings to reduce attack surface.
Adobe Acrobat/Reader 20.005.30680 (20.x track) or 24.001.30187/24.003.20112 (24.x track) depending on your release track
- 1. Identify the installed Adobe Acrobat or Acrobat Reader version by navigating to Help > About (or pressing Ctrl+I)
- 2. For Adobe Acrobat: upgrade to version 20.005.30680 or later for the 20.x track, or version 24.001.30187 or later for the 24.x track
- 3. For Adobe Acrobat DC: upgrade to version 24.003.20112 or later
- 4. For Adobe Acrobat Reader: upgrade to version 20.005.30680 or later
- 5. For Adobe Acrobat Reader DC: upgrade to version 24.003.20112 or later
- 6. Download updates from the official Adobe Acrobat download page at adobe.com or use the built-in Help > Check for Updates feature
- 7. Restart the application after applying the update
- 8. Verify the installed version matches or exceeds the fixed version numbers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-45112 — 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-45112 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