dbcve.org
Acrobat DcApplication · Adobe

CVE-2022-35672

HIGH · 7.8 CVSS v3.1 Published 2022-07-27
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
Adobe Acrobat Reader version 22.001.20085 (and earlier), 20.005.30314 (and earlier) and 17.012.30205 (and earlier) are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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

This is an out-of-bounds read vulnerability in Adobe Acrobat Reader that occurs when parsing a specially crafted PDF file. The vulnerability allows reading past the end of an allocated memory structure, which could potentially be leveraged for arbitrary code execution in the context of the current user. Successful exploitation requires user interaction in that a victim must open a malicious file.

MitigationUpdate Adobe Acrobat Reader to a version newer than 22.001.20085, 20.005.30314, or 17.012.30205, and exercise caution when 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:>= 20.001.30005, <= 20.005.30314>= 20.001.30005, <= 20.005.30311>= 17.011.30059, <= 17.012.30205
Acrobat ReaderApplication
Affected:>= 20.001.30005, <= 20.005.30314>= 20.001.30005, <= 20.005.30311>= 17.011.30059, <= 17.012.30205

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. Check Adobe Acrobat or Reader installed version
    Open the application, then go to Help > About Adobe Acrobat (or Reader). Alternatively, on Windows check the registry key HKLM\SOFTWARE\Adobe\Adobe Acrobat\[version]\InstallPath or locate the executable (acrord32.exe or acrobat.exe) and view its properties. On macOS, right-click the app and select Get Info.
    Affected if The version falls within 15.008.20082 to 22.001.20085, 20.001.30005 to 20.005.30314, 20.001.30005 to 20.005.30311, or 17.011.30059 to 17.012.30205.
  2. Confirm product variant and build number
    Identify whether you have Adobe Acrobat (commercial) or Adobe Acrobat Reader (free), and note the exact four-part build number (for example, 22.001.20085). The version ranges differ slightly between products.
    Affected if The exact version matches any of the affected ranges listed for your product variant.
  3. Verify PDF handling capability is in use
    This vulnerability is triggered during PDF parsing. Check if the application is used to open PDF files, particularly from external or untrusted sources. No special configuration check is needed as the vulnerability lies in the PDF parsing engine itself.
    Affected if Adobe Acrobat or Reader is installed within the affected version range and is used to open PDF files.

You are affected if Adobe Acrobat or Acrobat Reader is installed with a version between 15.008.20082 and 22.001.20085 (DC Classic/Continuous), between 20.001.30005 and 20.005.30314 (2020), or between 17.011.30059 and 17.012.30205 (2017), and the application is used to open PDF documents.

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 to a version newer than 22.001.20085, 20.005.30314, or 17.012.30205, and exercise caution when opening PDF files from untrusted sources.

Recommended fix High confidence

Adobe Acrobat/Reader 22.001.20093+, 20.005.30334+, or 17.012.30213+ (depending on your release track)

  1. 1. Verify the current Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat Reader (or About Adobe Acrobat).
  2. 2. 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.
  3. 3. Close all instances of Adobe Acrobat or Reader before running the installer.
  4. 4. Run the downloaded installer and follow the on-screen prompts to complete the update.
  5. 5. After installation, verify the version matches or exceeds the fixed releases: 22.001.20093 or later for the 2022 track, 20.005.30334 or later for the 2020 track, and 17.012.30213 or later for the 2017 track.
  6. 6. Ensure Adobe Auto-Update is enabled (Edit > Preferences > Updater > Automatically install updates) to receive future security patches.
Caveat Standard Adobe update - minimal risk; ensure adequate disk space and backup important PDFs before updating

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

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,620
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,592.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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