CVE-2022-44519
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 lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 an attacker to read sensitive memory contents by convincing a victim to open a specially crafted PDF file. The memory disclosure can be leveraged to bypass ASLR, potentially facilitating further exploitation.
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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/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.
-
Identify installed Adobe productOn Windows, open Add or Remove Programs and search for 'Adobe Acrobat' or 'Adobe Reader'. On macOS, check the Applications folder for Adobe Acrobat or Adobe Reader applications.Affected if Neither Adobe Acrobat nor Adobe Acrobat Reader is installed, the system is not affected.
-
Determine exact version numberFor Reader: Open the application, go to Help > About Adobe Acrobat Reader. For Acrobat: Open the application, go to Help > About Adobe Acrobat. Note the full version number displayed (for example, 22.001.20085).Affected if Unable to determine version, treat as potentially affected.
-
Compare version against affected rangesCheck if the installed version falls within: 15.008.20082 to 22.001.20085 (Acrobat/Reader DC); 17.011.30059 to 17.012.30205 (Acrobat/Reader 17.x); 20.001.30005 to 20.005.30314 or 20.005.30311 (Acrobat/Reader 20.x).Affected if Version is within any of these ranges, the system is affected by the vulnerability.
-
Confirm product typeVerify whether the installed product is Adobe Acrobat (paid) or Adobe Acrobat Reader (free). Both product lines share the same affected version ranges.Affected if Either product type with a version in the affected ranges is vulnerable.
A system is affected if Adobe Acrobat or Adobe Acrobat Reader is installed with a version number between the minimum and maximum values listed in the affected version ranges for the respective product line.
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 version. For versions 22.x, upgrade past 22.001.20085; for 20.x, upgrade past 20.005.3031x; for 17.x, upgrade past 17.012.30205.
Adobe Acrobat/Reader 22.001.20086 or later (for 22.x branch); 20.005.30315 or later (for 20.x branch); 17.012.30206 or later (for 17.x branch)
- 1. Identify the installed Adobe Acrobat or Acrobat Reader version by opening the application, selecting Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
- 2. Determine which version branch your current installation belongs to (17.x, 20.x, or 22.x).
- 3. Navigate to the Adobe Acrobat security bulletin page at helpx.adobe.com for the most accurate and up-to-date fixed version information.
- 4. Download and install the appropriate fixed version for your product line: For version 22.x, install version 22.001.20086 or later; for version 20.x, install version 20.005.30315 or later; for version 17.x, install version 17.012.30206 or later.
- 5. After installation, verify the new version by checking Help > About to confirm the remediation.
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-44519 — 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-44519 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