CVE-2023-21608
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 · uneditedAdobe Acrobat Reader versions 22.003.20282 (and earlier), 22.003.20281 (and earlier) and 20.005.30418 (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 memory is accessed after it has been freed, allowing an attacker to corrupt memory and achieve arbitrary code execution. The vulnerability is triggered when a victim opens 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>= 15.008.20082, <= 22.003.20282>= 15.008.20082, <= 22.003.20281>= 15.008.20082, <= 22.003.20282>= 15.008.20082, <= 22.003.20281>= 20.001.30005, <= 20.005.30418>= 20.001.30005, <= 20.005.30418CVSS 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.
-
Verify Adobe Acrobat or Reader is installedCheck Windows Registry under HKLM\SOFTWARE\Adobe or HKCU\SOFTWARE\Adobe for Acrobat or Adobe Acrobat Reader entries, or look for acrobat.exe (Acrobat) or AcroRd32.exe (Reader) in Program Files directoriesAffected if If Adobe Acrobat or Adobe Acrobat Reader is present on the system
-
Determine installed version numberOpen the application, go to Help menu and select About Adobe Acrobat/Reader to display the version, or query the Windows Registry key HKLM\SOFTWARE\Adobe\Acrobat\Version for the installed version valueAffected if A version number is returned that needs comparison to affected ranges
-
Compare version against affected rangesMatch your installed version to these vulnerable ranges: Acrobat DC/Reader DC versions 15.008.20082 through 22.003.20282 (inclusive), Acrobat/Reader Classic versions 20.001.30005 through 20.005.30418 (inclusive)Affected if Your installed version falls within or overlaps any of these vulnerable ranges
You are affected if Adobe Acrobat or Reader is installed and its version number is between 15.008.20082 and 22.003.20282 for DC/Reader DC versions, or between 20.001.30005 and 20.005.30418 for Classic versions.
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 · scopedUpdate Adobe Acrobat Reader to the latest version as provided by Adobe's official security updates. Users should avoid opening untrusted PDF files until the update is applied.
Acrobat DC/Reader DC: upgrade to version 22.003.20283 or later; Acrobat/Reader 2020: upgrade to version 20.005.30434 or later
- 1. Verify current Adobe Acrobat/Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. For Acrobat DC/Acrobat Reader DC: Navigate to Adobe's official security bulletin at helpx.adobe.com/security.html or search for APSB23-01 (the security bulletin for this CVE).
- 3. Download the fixed version from the official Adobe download page at get.adobe.com/reader or get.adobe.com/acrobat.
- 4. Ensure you download version 22.003.20283 or later for DC products, and version 20.005.30434 or later for 2020 products.
- 5. Close all Adobe applications before running the installer.
- 6. Run the installer with administrator privileges and follow the on-screen prompts.
- 7. After installation, verify the version matches the fixed release (Help > About).
- 8. Restart the system to ensure all components are properly updated.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-21608 — 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-2023-21608 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