CVE-2022-28244
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) is affected by a violation of secure design principles through bypassing the content security policy, which could result in an attacker sending arbitrarily configured requests to the cross-origin attack target domain. Exploitation requires user interaction in which the victim needs to access a crafted PDF file on an attacker's server.
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 a Content Security Policy (CSP) bypass vulnerability that allows an attacker to send arbitrarily configured cross-origin requests by convincing a user to open a crafted PDF file. This is a secure design principle violation rather than a memory corruption issue, enabling attackers to target external domains through the victim's browser context.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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.
-
Locate installed Adobe Acrobat or Reader versionWindows: Open Adobe Acrobat/Reader, go to Help > About Adobe Acrobat/Reader. Alternatively, check registry key HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\Version or HKLM\SOFTWARE\Adobe\Adobe Reader\DC\Version. macOS: Right-click the application in /Applications and select Get Info.Affected if Version falls within any of the affected ranges: 15.008.20082 through 22.001.20085, 17.011.30059 through 17.012.30205, 20.001.30005 through 20.005.30314, or 20.001.30005 through 20.005.30311
-
Identify the specific Adobe product installedConfirm whether the installed product is Adobe Acrobat DC, Adobe Acrobat Reader DC, Adobe Acrobat (classic), or Adobe Acrobat Reader (classic) as the version numbering differs between product lines.Affected if The product is any of the listed affected products and the version matches the ranges above
-
Determine if PDF files with JavaScript or embedded content are processedThis vulnerability is triggered when a user opens a crafted PDF containing specially configured elements that bypass Content Security Policy. The vulnerability exists in the PDF rendering engine regardless of specific user settings.Affected if The affected version is installed and the application processes PDF files with embedded content or JavaScript
The user is affected if Adobe Acrobat or Reader DC/classic version falls within the listed ranges (15.008.20082-22.001.20085, 17.011.30059-17.012.30205, 20.001.30005-20.005.30314, or 20.001.30005-20.005.30311) and the application opens 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.
dbcve · scopedUpdate Adobe Acrobat Reader DC to a version newer than 22.001.20085, 20.005.3031x, or 17.012.30205 to address this CSP bypass vulnerability.
Acrobat DC/Reader DC: Upgrade to version 22.001.20086 or later (or latest 22.x release); Acrobat/Reader 20.x: Upgrade to 20.005.30315 or later; Acrobat/Reader 17.x: Upgrade to 17.012.30206 or later
- 1. Open Adobe Acrobat Reader DC or Adobe Acrobat on your system
- 2. Navigate to Help > Check for Updates or use the built-in update mechanism
- 3. Allow the application to check for and install available security updates
- 4. Alternatively, download the latest version from the official Adobe website at https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 5. Ensure you upgrade to a version higher than 22.001.20085, 20.005.30314, or 17.012.30205 depending on your product track
- 6. After updating, verify the version by going to Help > About Adobe Acrobat [Reader] DC
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-28244 — 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-28244 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