CVE-2023-44339
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.006.20360 (and earlier) and 20.005.30524 (and earlier) are affected by an out-of-bounds read 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 confidenceThis is an out-of-bounds read vulnerability in Adobe Acrobat Reader that allows reading memory beyond allocated buffer boundaries. The vulnerability can leak sensitive memory addresses, enabling attackers to potentially bypass ASLR (Address Space Layout Randomization) as a mitigation bypass primitive. 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.006.20380>= 15.008.20082, < 23.006.20380>= 20.001.30005, <= 20.005.30539>= 20.001.30005, < 20.005.30539CVSS 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.
-
Check if Adobe Acrobat or Reader is installedOn Windows, check Start Menu for Adobe Acrobat or Adobe Acrobat Reader, or look in C:\Program Files\Adobe\ or C:\Program Files (x86)\Adobe\. On Mac, check /Applications for Adobe Acrobat or Adobe Reader.Affected if Adobe Acrobat or Adobe Acrobat Reader is present on the system
-
Determine the installed version numberRight-click the Adobe application shortcut and select Properties, then look at the Details tab for the Product Version. Alternatively, open the application, go to Help > About Adobe Acrobat Reader to see the exact version.Affected if Version cannot be determined or is in the format 15.x, 20.x, 22.x, or 23.x within the affected ranges
-
Compare version against affected rangesCheck if the installed version falls within: 15.008.20082 to 23.006.20379 (for DC versions), or 20.001.30005 to 20.005.30538 (for 2020 versions). Note that versions 23.006.20380 and above, and 20.005.30524 and above are fixed.Affected if Installed version is >= 15.008.20082 and < 23.006.20380 for DC line, OR >= 20.001.30005 and < 20.005.30539 for 2020 line
The environment is affected if Adobe Acrobat or Adobe Acrobat Reader is installed with a version number within the vulnerable ranges and the user opens untrusted PDF files.
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.3053923.006.20380
Update Adobe Acrobat Reader to the latest version beyond 23.006.20360 and 20.005.30524. Since exploitation requires user interaction, train users to avoid opening untrusted PDF files from unknown sources.
Adobe Acrobat/Reader DC: 23.006.20380 or later; Adobe Acrobat/Reader Classic 2020: 20.005.30540 or later
- 1. Verify current Adobe Acrobat or Adobe Reader version by opening the application, selecting Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. For Adobe Acrobat/Reader DC (Continuous): If version is 23.006.20360 or earlier, upgrade to version 23.006.20380 or later.
- 3. For Adobe Acrobat/Reader Classic 2020 (20.x): If version is 20.005.30539 or earlier, upgrade to version 20.005.30540 or later.
- 4. Download the latest version from the official Adobe website or use the built-in update mechanism (Help > Check for Updates).
- 5. Restart the application after installation and verify the version has been updated successfully.
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-44339 — 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-44339 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