CVE-2021-35984
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 · uneditedAcrobat Reader DC versions 2021.005.20054 (and earlier), 2020.004.30005 (and earlier) and 2017.011.30197 (and earlier) are affected by a Null pointer dereference vulnerability. An authenticated attacker could leverage this vulnerability achieve an application denial-of-service in the context of the current user. Exploitation of this issue does not requires user interaction.
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 confidenceA null pointer dereference vulnerability in Adobe Acrobat Reader DC versions 2021.005.20054 and earlier, 2020.004.30005 and earlier, and 2017.011.30197 and earlier allows an authenticated attacker to cause an application denial-of-service without user interaction.
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>= 15.008.20082, <= 21.005.20054>= 17.011.30059, <= 17.011.30197>= 20.001.30005, <= 20.004.30005>= 15.008.20082, <= 21.005.20054>= 17.011.30059, <= 17.011.30197>= 20.001.30005, <= 20.004.30005CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Adobe Acrobat Reader DC version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\DC\Version, or run 'powershell (Get-ItemProperty 'HKLM:\SOFTWARE\Adobe\Acrobat Reader\DC\Version').Version'Affected if Version number falls between 15.008.20082 and 21.005.20054 inclusive, OR between 17.011.30059 and 17.011.30197 inclusive, OR between 20.001.30005 and 20.004.30005 inclusive
-
Identify Adobe Acrobat Reader DC version on macOSOpen Finder, go to Applications, right-click Adobe Acrobat Reader DC, select Get Info, and check the Version field under GeneralAffected if Version number falls between 15.008.20082 and 21.005.20054 inclusive, OR between 17.011.30059 and 17.011.30197 inclusive, OR between 20.001.30005 and 20.004.30005 inclusive
-
Verify version using command lineOn Windows, run 'AcroRd32.exe /version' or check the executable properties. On macOS, run 'defaults read /Applications/Adobe\ Acrobat\ Reader\ DC.app/Contents/Info CFBundleVersion' in TerminalAffected if Version number falls between 15.008.20082 and 21.005.20054 inclusive, OR between 17.011.30059 and 17.011.30197 inclusive, OR between 20.001.30005 and 20.004.30005 inclusive
The environment is affected if Adobe Acrobat Reader DC is installed with a version number within any of the three vulnerable ranges: 15.008.20082-21.005.20054, 17.011.30059-17.011.30197, or 20.001.30005-20.004.30005.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpdate Adobe Acrobat Reader DC to a version later than the affected releases (2021.005.20054, 2020.004.30005, or 2017.011.30197 depending on the track).
Adobe Acrobat/Reader DC versions 2021.006.20034+ (Continuous track), 2021.001.10535+ (Classic 2021 track), 2020.005.30034+ (Classic 2020 track), or 2017.011.30198+ (Classic 2017 track) - or migrate to latest available release
- 1. Verify current Adobe Acrobat or Adobe Acrobat Reader DC version by opening the application and navigating to Help > About Adobe Acrobat/Reader DC
- 2. Close all Adobe applications
- 3. Download the latest version of Adobe Acrobat DC or Adobe Acrobat Reader DC from the official Adobe website (get.adobe.com/reader for Reader or get.adobe.com/acrobat for Pro)
- 4. Run the installer and follow the prompts to complete the installation
- 5. Restart the system after installation completes
- 6. Confirm the new version is installed by checking Help > About Adobe Acrobat/Reader DC
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-35984 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-35984 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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