CVE-2022-35667
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.20169 (and earlier), 20.005.30362 (and earlier) and 17.012.30249 (and earlier) are affected by an out-of-bounds write 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 an out-of-bounds write vulnerability in versions 22.001.20169 and earlier, 20.005.30362 and earlier, and 17.012.30249 and earlier. This memory corruption flaw allows arbitrary code execution when a user opens a specially crafted malicious PDF file, running with the privileges 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.20169>= 15.008.20082, <= 22.001.20169>= 20.001.30005, <= 20.005.30362>= 17.011.30059, <= 17.012.30249>= 20.001.30005, <= 20.005.30362>= 17.011.30059, <= 17.012.30249CVSS 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 will be displayed in the dialog box. Alternatively, on Windows check Programs and Features; on macOS check Applications folder.Affected if Adobe Acrobat Reader or Adobe Acrobat is installed
-
Determine exact version numberNote the full version number shown in the About dialog (for example, 22.001.20169 or 20.005.30334). Ensure you capture the complete three-part version including the middle and last segments.Affected if Version number cannot be determined or the product is not installed
-
Compare version against affected rangesCheck if your version falls within any of these ranges: 15.008.20082 through 22.001.20169 (DC variants), 20.001.30005 through 20.005.30362 (Acrobat/Reader 20.x), or 17.011.30059 through 17.012.30249 (Acrobat/Reader 17.x). Versions within these ranges are vulnerable.Affected if Installed version is greater than or equal to 15.008.20082 AND less than or equal to 22.001.20169 for DC; OR greater than or equal to 20.001.30005 AND less than or equal to 20.005.30362 for version 20.x; OR greater than or equal to 17.011.30059 AND less than or equal to 17.012.30249 for version 17.x
Your environment is affected if Adobe Acrobat Reader or Adobe Acrobat is installed with a version number within the vulnerable ranges listed above.
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 patched version. Until patched, advise users not to open untrusted or unexpected PDF files from unknown sources.
Acrobat DC (22.x): 22.001.20193+ | Acrobat 2020 (20.x): 20.005.30414+ | Acrobat 2017 (17.x): 17.012.30260+
- 1. Identify the installed Adobe Acrobat or Acrobat Reader version from the Help > About menu
- 2. For Acrobat DC (Continuous): Upgrade to version 22.001.20193 or later
- 3. For Acrobat 2020 (Classic): Upgrade to version 20.005.30414 or later
- 4. For Acrobat 2017 (Classic): Upgrade to version 17.012.30260 or later
- 5. Download the appropriate update from helpx.adobe.com or use Adobe's auto-update feature
- 6. Restart the application after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-35667 — 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-35667 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