CVE-2022-27792
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 · uneditedAcrobat Reader DC versions 22.001.20085 (and earlier), 20.005.3031x (and earlier) and 17.012.30205 (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 DC contains an out-of-bounds write vulnerability in parsing of malicious PDF files. An attacker can craft a PDF that triggers a buffer overflow, allowing arbitrary code execution in the context of the current user. User interaction is required (opening the malicious 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.20085>= 15.008.20082, <= 22.001.20085>= 17.011.30059, <= 17.012.30205>= 20.001.30005, <= 20.005.30314>= 20.001.30005, <= 20.005.30311>= 17.011.30059, <= 17.012.30205>= 20.001.30005, <= 20.005.30314>= 20.001.30005, <= 20.005.30311CVSS 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.0/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 if Adobe Acrobat or Reader is installedWindows: Check for 'Adobe Acrobat DC' or 'Adobe Acrobat Reader DC' in Programs and Features, or look in C:\Program Files\Adobe. macOS: Check /Applications for Adobe Acrobat or Adobe Acrobat Reader.Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
-
Determine the installed version on WindowsOpen Adobe Acrobat/Reader, go to Help > About Adobe Acrobat/Reader, or check the Windows Registry under HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\Version or HKLM\SOFTWARE\WOW6432Node\Adobe\Adobe Acrobat\DC\VersionAffected if The version falls within any of the affected ranges: 15.008.20082 to 22.001.20085, 17.011.30059 to 17.012.30205, or 20.001.30005 to 20.005.30314/30311
-
Determine the installed version on macOSOpen Adobe Acrobat/Reader and go to Adobe Acrobat/Reader > About Adobe Acrobat/Reader, or right-click the app in Applications and select Get Info to view the version numberAffected if The version falls within any of the affected ranges: 15.008.20082 to 22.001.20085, 17.011.30059 to 17.012.30205, or 20.001.30005 to 20.005.30314/30311
-
Verify the product line and channel versionConfirm whether the installation is Adobe Acrobat (standard/Pro) or Adobe Acrobat Reader, and identify if it is the Continuous track (DC) or the Classic track (traditional version numbers) based on the product name and version formatAffected if The product matches Adobe Acrobat DC, Adobe Acrobat Reader DC, Adobe Acrobat, or Adobe Acrobat Reader with a version in the affected ranges
If Adobe Acrobat or Adobe Acrobat Reader is installed and its version falls within 15.008.20082-22.001.20085, 17.011.30059-17.012.30205, or 20.001.30005-20.005.30314/30311, the environment is affected by this vulnerability.
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 DC to a version newer than 22.001.20085, 20.005.3031x, or 17.012.30205. Avoid opening untrusted PDF files.
Adobe Acrobat DC 22.001.20093 or later; Adobe Acrobat Reader DC 22.001.20093 or later (or corresponding later versions for Classic and 2020 tracks)
- Verify current Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader/Acrobat
- Close all Adobe applications completely
- Download the latest version of Adobe Acrobat or Acrobat Reader from the official Adobe website (get.adobe.com/reader for Reader, or adobe.com for Acrobat)
- Run the installer and follow the prompts to complete the installation
- Restart the computer after installation completes
- Verify the installed version is beyond 22.001.20085 for DC versions, or beyond 20.005.30314/17.012.30205 for classic tracks
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-2022-27792 — 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-27792 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