dbcve.org
Acrobat DcApplication · Adobe

CVE-2022-35671

MEDIUM · 5.5 CVSS v3.1 Published 2022-08-11
Fix available
A fix is available. Upgrade to after 22.001.20169 or later.
See remediation →
58/100
Remediation priority · Elevated
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 versions 22.001.20169 (and earlier), 20.005.30362 (and earlier) and 17.012.30249 (and earlier) are affected by an out-of-bounds read 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 · moderate confidence

Adobe Acrobat Reader contains an out-of-bounds read vulnerability that allows reading memory beyond allocated buffers. This can expose sensitive memory contents and assist attackers in bypassing ASLR mitigations. Successful exploitation requires a victim to open a specially crafted malicious PDF file.

MitigationApply vendor-supplied security patches to update Adobe Acrobat Reader to a version beyond 22.001.20169, 20.005.30362, or 17.012.30249. Consider disabling JavaScript in Acrobat Reader and deploying endpoint detection capabilities to identify malicious PDF files.

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.20169
Acrobat Reader DcApplication
Affected:>= 15.008.20082, <= 22.001.20169
AcrobatApplication
Affected:>= 20.001.30005, <= 20.005.30362>= 17.011.30059, <= 17.012.30249
Acrobat ReaderApplication
Affected:>= 20.001.30005, <= 20.005.30362>= 17.011.30059, <= 17.012.30249

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

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

  1. Verify Adobe Acrobat Reader is installed
    On Windows, check Program Files\Adobe\Adobe Acrobat <version> or look in Programs and Features. On Mac, check /Applications for Adobe Acrobat Reader.app. Alternatively, open the application and check Help > About Adobe Acrobat Reader.
    Affected if Adobe Acrobat Reader is present on the system
  2. Determine the installed version number
    Open Adobe Acrobat Reader, then go to Help > About Adobe Acrobat Reader. The version number appears in the dialog (format like XX.XXX.XXXXX). Alternatively on Windows, check the registry key HKLM\SOFTWARE\Adobe\Acrobat Reader\<version>\InstallPath, or use PowerShell: Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*Adobe Acrobat Reader*'} | Select-Object DisplayName, DisplayVersion
    Affected if A version number is found matching the affected ranges
  3. Compare version against affected ranges
    Check if your installed version falls within any of these ranges: 15.008.20082 to 22.001.20169 (2022 track), 20.001.30005 to 20.005.30362 (2020 track), or 17.011.30059 to 17.012.30249 (2017 track). The first number indicates the release year (15=2015, 17=2017, 20=2020, 22=2022).
    Affected if Installed version is greater than or equal to the lower bound AND less than or equal to the upper bound of any affected range

You are affected if Adobe Acrobat Reader is installed and its version falls within 15.008.20082-22.001.20169, 20.001.30005-20.005.30362, or 17.011.30059-17.012.30249.

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.20169
Interim mitigation

Apply vendor-supplied security patches to update Adobe Acrobat Reader to a version beyond 22.001.20169, 20.005.30362, or 17.012.30249. Consider disabling JavaScript in Acrobat Reader and deploying endpoint detection capabilities to identify malicious PDF files.

Recommended fix High confidence

Upgrade to Acrobat Reader/Acrobat DC version 22.001.20170 or later, 20.005.30363 or later, or 17.012.30250 or later (or latest available version)

  1. 1. Open Adobe Acrobat Reader or Adobe Acrobat DC
  2. 2. Navigate to Help > Check for Updates (or use the Help menu)
  3. 3. Allow the application to check for available updates
  4. 4. If updates are available, review the update details to confirm it addresses security vulnerabilities
  5. 5. Download and install all recommended security updates
  6. 6. Alternatively, manually download the latest version from the official Adobe website at get.adobe.com/reader or get.adobe.com/acrobat
  7. 7. After installation, verify the version by going to Help > About Adobe Acrobat Reader (or About Adobe Acrobat)
  8. 8. Confirm the version number is above 22.001.20169, above 20.005.30362, or above 17.012.30249 depending on your product track
Caveat Standard upgrade risk - minor version differences typically have no breaking changes for end users

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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