CVE-2022-34239
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.001.20142 (and earlier), 20.005.30334 (and earlier) and 17.012.30229 (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 buffers. The vulnerability can leak sensitive memory contents and potentially bypass ASLR (Address Space Layout Randomization), a key memory protection mechanism. Exploitation requires a victim to open a 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.001.20142>= 15.008.20082, <= 22.001.20142>= 20.001.30005, <= 20.005.30334>= 20.001.30005, <= 20.005.30331>= 17.011.30059, <= 17.012.30229>= 17.011.30059, <= 17.012.30227>= 20.001.30005, <= 20.005.30334>= 20.001.30005, <= 20.005.30331>= 17.011.30059, <= 17.012.30229>= 17.011.30059, <= 17.012.30227CVSS 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 product is installedOpen Windows Control Panel > Programs and Features, or check C:\Program Files\Adobe for Adobe Acrobat or Adobe Acrobat Reader foldersAffected if Adobe Acrobat Reader or Adobe Acrobat is present on the system
-
Obtain installed version numberOpen Adobe Acrobat Reader or Adobe Acrobat, go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to display the exact version stringAffected if Unable to retrieve version indicates product may not be standard installation
-
Confirm version falls within affected range for DC productsCompare your version to these ranges: 15.008.20082 through 22.001.20142 for Acrobat/Reader DC Classic or ContinuousAffected if Version number is greater than or equal to 15.008.20082 AND less than or equal to 22.001.20142
-
Confirm version falls within affected range for 2020 productsCompare your version to: 20.001.30005 through 20.005.30334, or 20.001.30005 through 20.005.30331 for different tracksAffected if Version number is between 20.001.30005 and 20.005.30334 (or 20.005.30331 depending on track)
-
Confirm version falls within affected range for 2017 productsCompare your version to: 17.011.30059 through 17.012.30229, or 17.011.30059 through 17.012.30227 for different tracksAffected if Version number is between 17.011.30059 and 17.012.30229 (or 17.012.30227 depending on track)
Your environment is affected if Adobe Acrobat Reader or Adobe Acrobat is installed AND its version falls within any of the listed vulnerable ranges, making the application susceptible to out-of-bounds read when processing malicious 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.
From vendor dataUpdate Adobe Acrobat Reader to the latest version beyond the affected releases (22.001.20142, 20.005.30334, 17.012.30229). Implement file-based screening and user training to reduce risk from malicious PDF files.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34239 — 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-2022-34239 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