CVE-2022-44514
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.20085 (and earlier), 20.005.3031x (and earlier) and 17.012.30205 (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 allows arbitrary code execution when a victim opens a specially crafted malicious PDF file. The vulnerability exists due to improper memory management, enabling an attacker to free memory and then access it after it has been deallocated.
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.
-
Identify installed Adobe productOpen Adobe Acrobat Reader or Adobe Acrobat, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to view the exact version numberAffected if The product is Adobe Acrobat Reader DC or Adobe Acrobat DC and the version shown falls within the affected ranges
-
Check DC version against affected rangeCompare your displayed version to the DC range: 15.008.20082 through 22.001.20085 (all versions from 15.008.20082 up to and including 22.001.20085 are affected)Affected if The installed version is greater than or equal to 15.008.20082 AND less than or equal to 22.001.20085
-
Check non-DC version against first affected rangeCompare your displayed version to the range: 17.011.30059 through 17.012.30205Affected if The installed version is between 17.011.30059 and 17.012.30205 inclusive
-
Check non-DC version against second affected rangeCompare your displayed version to the range: 20.001.30005 through 20.005.30314 or 20.005.30311Affected if The installed version is between 20.001.30005 and 20.005.30314 inclusive, or between 20.001.30005 and 20.005.30311 inclusive
You are affected if Adobe Acrobat Reader DC or Adobe Acrobat DC is installed with a version number within any of the listed affected ranges, and the vulnerability is triggered when opening a specially crafted malicious PDF file.
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 and disable JavaScript in Acrobat Reader settings.
Adobe Acrobat/Reader 22.001.20086 or later for Continuous track; 20.005.30315 or later for Classic 2020 track; 17.012.30206 or later for Classic 2017 track
- 1. Open Adobe Acrobat or Acrobat Reader application
- 2. Navigate to Help > Check for Updates (or use the menu specific to your OS)
- 3. Allow the application to check for available updates
- 4. If updates are available, review the update details to confirm it includes the security fix for CVE-2022-44514
- 5. Download and install the recommended update
- 6. Restart the application after installation
- 7. Verify the version has been updated by going to Help > About Adobe Acrobat (or Reader)
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-44514 — 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-44514 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