dbcve.org
Acrobat DcApplication · Adobe

CVE-2022-24102

HIGH · 7.8 CVSS v3.1 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 exploits memory that has been freed but is still referenced, potentially enabling an attacker to execute code in the context of the current user.

MitigationUpdate Adobe Acrobat Reader DC to the latest patched version (22.001.20085 or later for the Continuous track, 20.005.30334 or later for the Classic track) to remediate this vulnerability.

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. Verify Adobe Acrobat or Reader is installed
    Check the Windows registry for Adobe Acrobat entries under HKLM\SOFTWARE\Adobe\ or look for AcroRd32.exe (Reader) or AcroBat.exe (Acrobat) in typical installation paths such as C:\Program Files\Adobe\Adobe Acrobat [version]\
    Affected if Either Adobe Acrobat or Adobe Acrobat Reader is present on the system
  2. Locate the main executable file
    Find the installed executable: for Reader, look for AcroRd32.exe in the installation directory; for Acrobat, look for AcroBat.exe. The default path is typically C:\Program Files\Adobe\Adobe Acrobat [version]\
    Affected if The executable file exists on the system
  3. Retrieve the installed version number
    Right-click the executable file (AcroRd32.exe or AcroBat.exe), select Properties, then view the Details tab to find the Product version field. Alternatively, query the registry key HKLM\SOFTWARE\Adobe\Adobe Acrobat\[version]\InstallPath for the version information
    Affected if A version number is returned from the executable or registry
  4. Determine the product track and compare to affected versions
    Compare your installed version number against the affected ranges: for DC track (Continuous): 15.008.20082 through 22.001.20085; for Classic 2017: 17.011.30059 through 17.012.30205; for Classic 2020: 20.001.30005 through 20.005.30314 (Acrobat) or 20.005.30311 (Reader)
    Affected if The installed version falls within any of the listed affected ranges (15.008.20082-22.001.20085 for DC, 17.011.30059-17.012.30205 for 2017, or 20.001.30005-20.005.30314/30311 for 2020)

If Adobe Acrobat or Reader is installed and the version falls within the affected ranges listed, the system is potentially vulnerable to CVE-2022-24102 when opening malicious PDF files.

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 (22.001.20085 or later for the Continuous track, 20.005.30334 or later for the Classic track) to remediate this vulnerability.

Recommended fix High confidence

Adobe Acrobat DC / Acrobat Reader DC version 22.001.20093 or later (or latest available version)

  1. 1. Close all instances of Adobe Acrobat or Acrobat Reader.
  2. 2. Navigate to the Adobe Acrobat download page or use Adobe's official update mechanism.
  3. 3. Download and install the latest version of Adobe Acrobat DC or Acrobat Reader DC.
  4. 4. Alternatively, open Acrobat Reader DC, go to Help > Check for Updates to receive the latest security patch.
  5. 5. Verify the installed version is above 22.001.20085 (e.g., 22.001.20093 or later).
Caveat Standard upgrade; ensure compatibility with any existing plugins or workflows

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-24102 — 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-24102 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