CVE-2023-29303
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 23.003.20244 (and earlier) and 20.005.30467 (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 attackers to read sensitive memory contents and potentially bypass ASLR security mitigations. Exploitation requires a victim to open a maliciously crafted 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, < 23.003.20269>= 15.008.20082, < 23.003.20269>= 20.001.30005, <= 20.005.30516.10516>= 20.001.30005, < 20.005.30514.10514>= 20.001.30005, < 20.005.30516.10516>= 20.001.30005, < 20.005.30514.10514CVSS 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.
-
Confirm Adobe Acrobat or Reader is installedOpen Windows Settings > Apps > Apps & features, or use Control Panel > Programs and Features. Look for Adobe Acrobat DC, Adobe Acrobat Reader DC, Adobe Acrobat, or Adobe Acrobat Reader in the installed programs list.Affected if No Adobe Acrobat or Reader product is listed in installed programs (not vulnerable - product not present)
-
Locate the installed Acrobat executableNavigate to the Adobe installation directory, typically C:\Program Files\Adobe\Acrobat DC\ or C:\Program Files (x86)\Adobe\Acrobat Reader DC\. Identify the main executable: AcroRd32.exe for Reader, or Acro.exe for Acrobat.Affected if Executable not found at expected paths (not vulnerable - product may be installed differently or removed)
-
Retrieve the file versionRight-click the identified executable (AcroRd32.exe or Acro.exe), select Properties, then go to the Details tab. Note the Product version and File version values.Affected if Unable to retrieve version information from executable properties
-
Compare installed version against affected rangesDocument the full version number (e.g., 22.001.20620 for 22.x branch, or 20.005.30516 for 20.x branch). Compare against: 15.008.20082 to 23.003.20268 (23.x branch), 20.001.30005 to 20.005.30516.10516 or 20.005.30514.10513 (20.x branch).Affected if Installed version falls within: >= 15.008.20082 and < 23.003.20269 for 23.x branch; OR >= 20.001.30005 and < 20.005.30516.10516 (or < 20.005.30514.10514) for 20.x branch
The environment is affected if Adobe Acrobat or Reader is installed with a version number matching the ranges 15.008.20082 to 23.003.20268 (Continuous/2023 track) or 20.001.30005 to 20.005.30516.10516 (Classic 2020 track), and the victim opens a malicious PDF file.
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.30514.1051420.005.30516.1051623.003.20269
Update Adobe Acrobat Reader to version 23.003.20245 or later for the 23.x branch, or version 20.005.30468 or later for the 20.x branch. Avoid opening untrusted PDF files from unknown sources.
Adobe Acrobat Reader/Acrobat Continuous: >=23.003.20269; Classic 2020: >=20.005.30516
- Open Adobe Acrobat Reader or Acrobat on your system
- Navigate to Help > Check for Updates (or use the Help menu)
- Allow Adobe to check for and install the latest updates
- Alternatively, download the latest version from the official Adobe website: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- After updating, verify the version by going to Help > About Adobe Acrobat Reader (or About Adobe Acrobat)
- Confirm the version number meets the minimum fixed releases: 23.003.20269 or higher for Continuous track, or 20.005.30516 or higher for Classic 2020 track
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-29303 — 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-29303 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