CVE-2021-28558
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 versions 2021.001.20150 (and earlier), 2020.001.30020 (and earlier) and 2017.011.30194 (and earlier) are affected by an Heap-based buffer overflow vulnerability in the PDFLibTool component. An unauthenticated attacker could leverage this vulnerability to achieve 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 confidenceHeap-based buffer overflow vulnerability in Adobe Acrobat Reader DC's PDFLibTool component allows an unauthenticated attacker to achieve arbitrary code execution through a malicious PDF file opened by the victim.
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.001.20150>= 15.008.20082, <= 21.001.20150>= 17.011.30059, <= 17.011.30194>= 20.001.30005, <= 20.001.30020>= 17.011.30059, <= 17.011.30194>= 20.001.30005, <= 20.001.30020CVSS 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
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify if Adobe Acrobat/Reader DC (2021 track) is installedLook for Adobe Acrobat DC or Adobe Acrobat Reader DC in the system's installed programs list, or check the product information within the application Help > About menuAffected if The product is installed and the version number falls between 15.008.20082 and 21.001.20150 inclusive
-
Determine the installed version of Acrobat/Reader DC (2021 track)Open the application, go to Help > About Adobe Acrobat/Reader DC, or view the version in the Windows Programs and Features listAffected if The displayed version is greater than or equal to 15.008.20082 AND less than or equal to 21.001.20150
-
Identify if Adobe Acrobat or Acrobat Reader (2017 track) is installedLook for Adobe Acrobat 2017 or Adobe Acrobat Reader 2017 in installed programs, or check the application's About dialogAffected if The product is installed and the version is between 17.011.30059 and 17.011.30194 inclusive
-
Identify if Adobe Acrobat or Acrobat Reader (2020 track) is installedLook for Adobe Acrobat 2020 or Adobe Acrobat Reader 2020 in installed programs, or check the application's About dialogAffected if The product is installed and the version is between 20.001.30005 and 20.001.30020 inclusive
You are affected if any Adobe Acrobat or Adobe Acrobat Reader version installed on the system falls within any of the affected ranges: 15.008.20082-21.001.20150, 17.011.30059-17.011.30194, or 20.001.30005-20.001.30020.
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 newer than 2021.001.20150, 2020.001.30020, or 2017.011.30194 (depending on the track in use).
Upgrade to Adobe Acrobat Reader DC / Acrobat DC 2021.001.20154+ (or 2020.001.30025+ for 2020 track, or 2017.011.30210+ for 2017 track), or migrate to the latest continuous release
- 1. Identify the current Adobe Acrobat or Adobe Acrobat Reader DC version by navigating to Help > About Adobe Acrobat Reader DC (or About Adobe Acrobat).
- 2. Determine which track your installation belongs to: 2021 (21.xxx), 2020 (20.xxx), or 2017 (17.xxx) based on the version number.
- 3. For the 2021 track: Download and install version 2021.001.20154 or later from the Adobe Acrobat download page.
- 4. For the 2020 track: Download and install version 2020.001.30025 or later from the Adobe Acrobat download page.
- 5. For the 2017 track: Download and install version 2017.011.30210 or later from the Adobe Acrobat download page.
- 6. Alternatively, enable automatic updates: Go to Edit > Preferences > Updater and select 'Automatically install updates'.
- 7. After installation, restart the application and verify the version has been updated to a fixed release.
- 8. Educate users to avoid opening untrusted PDF files from unknown sources, as exploitation requires user interaction.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-28558 — 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-28558 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