dbcve.org
Acrobat DcApplication · Adobe

CVE-2022-44512

HIGH · 7.8 CVSS v3.1 Published 2024-12-19
Fix available
A fix is available. Upgrade to after 22.001.20085 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
Acrobat Reader DC version 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 confidence

Adobe Acrobat Reader DC contains an out-of-bounds write vulnerability in parsing of malicious PDF files. Successful exploitation allows arbitrary code execution in the context of the current user. The vulnerability affects versions 22.001.20085 and earlier, 20.005.3031x and earlier, and 17.012.30205 and earlier.

MitigationUpdate Adobe Acrobat Reader DC to the latest patched version. Users should avoid opening PDF files from untrusted sources.

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
Acrobat DcApplication
Affected:>= 15.008.20082, <= 22.001.20085
Acrobat Reader DcApplication
Affected:>= 15.008.20082, <= 22.001.20085
AcrobatApplication
Affected:>= 17.011.30059, <= 17.012.30205>= 20.001.30005, <= 20.005.30314>= 20.001.30005, <= 20.005.30311
Acrobat ReaderApplication
Affected:>= 17.011.30059, <= 17.012.30205>= 20.001.30005, <= 20.005.30314>= 20.001.30005, <= 20.005.30311

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Adobe product
    Open Adobe Acrobat Reader DC or Adobe Acrobat DC. Click Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to see which product is installed.
    Affected if Product is Adobe Acrobat Reader DC, Adobe Acrobat DC, Adobe Acrobat, or Adobe Acrobat Reader.
  2. Find installed version number
    In the About dialog, record the full version number displayed (for example: 22.001.20085, 20.005.30314, 17.012.30205).
    Affected if A version number is displayed in the About window.
  3. Compare version to affected ranges
    Compare your recorded version to these ranges: 15.008.20082 through 22.001.20085 (Acrobat/Reader DC); 17.011.30059 through 17.012.30205; 20.001.30005 through 20.005.30314 or 20.005.30311.
    Affected if Your installed version falls within any of these ranges.

You are affected if Adobe Acrobat Reader DC, Adobe Acrobat DC, Adobe Acrobat, or Adobe Acrobat Reader is installed with a version between 15.008.20082 and 22.001.20085, or within the specific 17.x or 20.x ranges listed.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 22.001.20085
Interim mitigation

Update Adobe Acrobat Reader DC to the latest patched version. Users should avoid opening PDF files from untrusted sources.

Recommended fix Moderate confidence

Upgrade to the latest available version of Adobe Acrobat/Acrobat Reader (22.x, 20.005.3031x+, or 17.012.30205+)

  1. 1. Determine the currently installed Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
  2. 2. Based on the installed major version line, identify the appropriate upgrade target: For version 22.x line, upgrade to a release newer than 22.001.20085; For version 20.x line, upgrade to a release newer than 20.005.3031x; For version 17.x line, upgrade to a release newer than 17.012.30205.
  3. 3. Download the latest version of Adobe Acrobat or Acrobat Reader from the official Adobe website at get.adobe.com/reader or get.adobe.com/acrobat.
  4. 4. Close all running instances of Adobe Acrobat or Acrobat Reader.
  5. 5. Run the downloaded installer and follow the on-screen prompts to complete the upgrade.
  6. 6. After installation, verify the new version by checking Help > About to confirm the vulnerability is patched.
Caveat Standard minor version upgrades typically have no breaking changes; ensure compatibility with any existing PDF workflows or plugins

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-44512 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-44512 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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