CVE-2022-34224
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 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 in versions 22.001.20142 and earlier, 20.005.30334 and earlier, and 17.012.30229 and earlier. An attacker can exploit this by crafting a malicious PDF file that, when opened by a victim, triggers the use-after-free condition leading to arbitrary code execution in the context of the current user.
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
- 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 installed Adobe productOpen Adobe Acrobat Reader or Acrobat, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). The version number will be displayed in the dialog box.Affected if The product is Adobe Acrobat Reader Dc, Adobe Acrobat Dc, Adobe Acrobat Reader, or Adobe Acrobat.
-
Record the full version numberNote the complete version string shown in the About dialog (for example: 22.001.20142, 20.005.30334, or 17.012.30229).Affected if A version number is displayed.
-
Compare version against affected rangesCheck if your version falls within any of these ranges: 15.008.20082 to 22.001.20142; 20.001.30005 to 20.005.30334; 20.001.30005 to 20.005.30331; 17.011.30059 to 17.012.30229; 17.011.30059 to 17.012.30227.Affected if Your installed version is within any of these ranges.
-
Confirm PDF handling is enabledVerify Adobe Acrobat Reader is set as the default PDF handler or can open PDF files. Open any PDF file to confirm the application processes them.Affected if PDF files can be opened in the installed Adobe product.
-
Check for user interaction with untrusted PDFsDetermine whether the system user opens PDF files from email attachments, web downloads, or other untrusted sources.Affected if Users routinely open PDF files from unverified or external sources using the affected Adobe product.
You are affected if Adobe Acrobat Reader or Adobe Acrobat is installed with a version number between 15.008.20082 and 22.001.20142 (for DC products) or within the older version ranges specified, and users open PDF files with it.
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 a version newer than the affected versions listed (22.001.20142, 20.005.30334, 17.012.30229). Avoid opening untrusted or unexpected PDF files from unverified sources.
Adobe Acrobat and Reader versions 22.001.20143+, 20.005.30335+, or 17.012.30230+ (or the latest current version from adobe.com)
- Open Adobe Acrobat or Acrobat Reader on your system
- Navigate to Help > Check for Updates (or use the built-in update mechanism)
- 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)
- Ensure you update to a version newer than 22.001.20142, 20.005.30334, or 17.012.30229 as listed in the advisory
- Verify the installed version by going to Help > About Adobe Acrobat Reader (or About Adobe Acrobat)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.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,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-34224 — 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-34224 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