CVE-2021-44712
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 version 21.007.20099 (and earlier), 20.004.30017 (and earlier) and 17.011.30204 (and earlier) are affected by an Access of Memory Location After End of Buffer vulnerability that could lead to application denial-of-service. 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 confidenceAdobe Acrobat Reader DC contains a buffer over-read vulnerability where the software accesses memory locations beyond the end of an allocated buffer when parsing specially crafted PDF files, leading to application denial-of-service.
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.007.20099>= 15.008.20082, <= 21.007.20099>= 17.011.30059, <= 17.011.30204>= 20.001.30005, <= 20.004.30017>= 17.011.30059, <= 17.011.30204>= 20.001.30005, <= 20.004.30017CVSS 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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 installed Adobe productOpen Adobe Acrobat or Reader, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). The product name (Acrobat vs Reader) and track (Continuous, Classic, 2017) will be displayed in the title bar or about dialog.Affected if The product is Adobe Acrobat or Adobe Acrobat Reader (not standalone Adobe Reader).
-
Determine exact version numberIn the About dialog, note the exact version number displayed (for example: 21.005.20093 or 20.004.30015). Record all three number groups.Affected if Version falls within ranges: 15.008.20082 to 21.007.20099, OR 17.011.30059 to 17.011.30204, OR 20.001.30005 to 20.004.30017.
-
Identify the release trackThe version number indicates the track: versions starting with 21.x or 20.x are Continuous track; versions 17.x are Classic or 2017 track. Check Adobe's documentation or the about dialog for track confirmation.Affected if Any track with version in affected ranges.
-
Confirm PDF processing is enabledVerify the software is configured to open PDF files. This is the default state. The vulnerability triggers when the software parses PDF content, so any system that opens PDF files with this software is potentially exposed.Affected if PDF files can be opened with the affected Adobe product (default configuration).
Your environment is affected if Adobe Acrobat or Adobe Acrobat Reader is installed with a version number matching the ranges: 15.008.20082-21.007.20099, 17.011.30059-17.011.30204, or 20.001.30005-20.004.30017.
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 the latest version (21.007.20099+ for Continuous track, 20.004.30017+ for Classic track, 17.011.30204+ for 2017 track). Avoid opening untrusted PDF files.
Acrobat DC/Reader DC: 21.008.20080+ (Continuous) or 21.001.20093+ (Classic) | Acrobat/Reader 2017: 17.012.20098+ | Acrobat/Reader 2020: 20.005.30034+
- 1. Open Adobe Acrobat or Adobe Acrobat Reader on the affected system
- 2. Navigate to Help > Check for Updates (or use the Help menu depending on your version)
- 3. Alternatively, download the latest security update directly from Adobe's official security bulletin page at helpx.adobe.com
- 4. Ensure you download version 21.008.20080 or later for Acrobat/Reader DC (Continuous track)
- 5. Ensure you download version 21.001.20093 or later for Acrobat/Reader DC (Classic track)
- 6. Ensure you download version 17.012.20098 or later for Acrobat/Reader 2017
- 7. Ensure you download version 20.005.30034 or later for Acrobat/Reader 2020
- 8. Restart the application after installation
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-44712 — 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-44712 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