CVE-2022-28242
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 version 22.001.2011x (and earlier), 20.005.3033x (and earlier) and 17.012.3022x (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 confidenceA use-after-free vulnerability in Adobe Acrobat Reader DC versions 22.001.2011x and earlier, 20.005.3033x and earlier, and 17.012.3022x and earlier allows arbitrary code execution in the context of the current user. Exploitation requires the victim to open a malicious PDF file, making social engineering a likely attack vector.
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.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.
-
Verify Adobe Acrobat or Reader is installedCheck for the application in the installed programs list (Windows: Control Panel > Programs and Features, macOS: Applications folder). Look for 'Adobe Acrobat DC', 'Adobe Acrobat Reader DC', 'Adobe Acrobat', or 'Adobe Acrobat Reader'.Affected if The application is not installed.
-
Identify the exact product name and versionOpen the application, then go to Help > About Adobe Acrobat (or About Adobe Reader). Alternatively, on Windows check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat\InstallPath for the version, or on macOS right-click the app in Applications and select Get Info to see the version number.Affected if No Adobe Acrobat or Reader product is found.
-
Compare the installed version to affected rangesFor Adobe Acrobat DC or Acrobat Reader DC: check if version is between 15.008.20082 and 22.001.20085 inclusive. For Adobe Acrobat/Reader (classic): check if version falls in 17.011.30059-17.012.30205, 20.001.30005-20.005.30314, or 20.001.30005-20.005.30311.Affected if The installed version falls within any of the listed affected ranges.
-
Confirm the vulnerability trigger conditionThe flaw is triggered when a user opens a specially crafted malicious PDF file. This is the exploitation vector, not an environment misconfiguration.Affected if N/A - this describes how the flaw is exploited, not a detection condition.
The environment is affected if Adobe Acrobat DC, Adobe Acrobat Reader DC, Adobe Acrobat, or Adobe Acrobat Reader is installed with a version number matching any of the listed affected ranges (15.008.20082-22.001.20085 for DC products, or the specified classic version ranges).
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 the latest patched version. Until patched, avoid opening PDF files from untrusted sources.
Adobe Acrobat Reader DC / Acrobat DC version 22.001.2012 or later; version 20.005.3034 or later; version 17.012.3023 or later (or migrate to latest available release)
- 1. Open Adobe Acrobat Reader DC or Adobe Acrobat on your system.
- 2. Navigate to Help > Check for Updates (or Help > About Adobe Acrobat Reader DC).
- 3. Allow the application to check for and install any available updates.
- 4. 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).
- 5. Verify the installed version by going to Help > About and confirm it is beyond the vulnerable versions: Reader DC should be > 22.001.2011, 20.005.3033, or 17.012.3022 depending on your release track; Acrobat should be > 22.001.20085, > 20.005.30314, or > 17.012.30205.
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-28242 — 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-28242 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