dbcve.org
Acrobat DcApplication · Adobe

CVE-2022-24104

HIGH · 7.8 CVSS v3.0 Published 2022-05-11
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 versions 20.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 confidence

A use-after-free vulnerability in Adobe Acrobat Reader DC allows arbitrary code execution when a victim opens a malicious PDF file. The vulnerability stems from improper memory management where the application continues using a pointer to memory that has been freed, potentially enabling an attacker to execute arbitrary code in the context of the current user's privileges.

MitigationUpdate Adobe Acrobat Reader DC to a version newer than 20.001.20085, 20.005.3031x, or 17.012.30205. In enterprise environments, deploy the patch via software distribution tools and verify completion across all endpoints.

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.0/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, then navigate to Help > About Adobe Acrobat Reader DC (or About Adobe Acrobat). Alternatively, on Windows check the registry key HKLM\SOFTWARE\Adobe\Acrobat DC\Version (or HKLM\SOFTWARE\Adobe\Acrobat\Version for older versions).
    Affected if The installed product is Adobe Acrobat Reader DC or Adobe Acrobat.
  2. Determine exact version number
    Note the full version number displayed in the About dialog or registry value. For DC versions, look for the format like 22.001.20085. For Classic versions, look for formats like 17.012.30205 or 20.005.30314.
    Affected if A version number is retrieved.
  3. Compare version against DC range
    If using a DC version (2020, 2021, 2022), verify whether the version falls between 15.008.20082 and 22.001.20085 inclusive.
    Affected if The DC version is >= 15.008.20082 and <= 22.001.20085.
  4. Compare version against Classic 17.x range
    If using a Classic version, check if the version is between 17.011.30059 and 17.012.30205 inclusive.
    Affected if The Classic version is >= 17.011.30059 and <= 17.012.30205.
  5. Compare version against Classic 20.x range
    If using a Classic 20.x version, verify whether the version is between 20.001.30005 and 20.005.30314 (or 20.005.30311) inclusive.
    Affected if The Classic 20.x version is >= 20.001.30005 and <= 20.005.30314 (or 20.005.30311).

The environment is affected if Adobe Acrobat Reader DC or Adobe Acrobat is installed with a version that falls within any of the listed affected ranges (15.008.20082-22.001.20085 for DC, 17.011.30059-17.012.30205 for Classic 17.x, or 20.001.30005-20.005.30314 for Classic 20.x).

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 a version newer than 20.001.20085, 20.005.3031x, or 17.012.30205. In enterprise environments, deploy the patch via software distribution tools and verify completion across all endpoints.

Recommended fix Moderate confidence

Upgrade to Adobe Acrobat DC 2022 (version 22.001.20093 or later), Adobe Acrobat DC 2020 (version 20.005.30318 or later), or Adobe Acrobat 2017 (version 17.012.30210 or later); for Reader, use corresponding Reader versions from the same release trains

  1. 1. Verify current Adobe Acrobat or Reader version by navigating to Help > About Adobe Acrobat/Reader
  2. 2. Download the latest version of Adobe Acrobat or Adobe Reader DC from the official Adobe website (get.adobe.com/reader for Reader, or adobe.com for Acrobat)
  3. 3. Close all Adobe applications and any applications that may have integrated PDF functionality
  4. 4. Run the downloaded installer and follow the on-screen prompts to complete the installation
  5. 5. Restart the computer after installation completes
  6. 6. Verify the installed version is beyond the vulnerable version boundaries: 20.005.30314 or later for Continuous track, 22.001.20085 or later for 2022 track, or 17.012.30205 or later for 2020 track
Caveat Large upgrades may require acceptance of new license terms; ensure compatibility testing with existing workflows before deploying enterprise-wide

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

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-24104 — 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-24104 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