CVE-2021-45068
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 out-of-bounds write vulnerability that could result in 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 confidenceAn out-of-bounds write vulnerability in Adobe Acrobat Reader DC allows arbitrary code execution with the current user's privileges. The flaw exists in specific legacy versions (21.007.20099 and earlier, 20.004.30017 and earlier, 17.011.30204 and earlier) and requires a victim to open a malicious PDF file to trigger exploitation.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Adobe Acrobat or Reader versionOn Windows, open Registry Editor and navigate to HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\Version (or HKLM\SOFTWARE\Adobe\Adobe Reader\DC\Version). Alternatively, open the application, go to Help > About Adobe Acrobat (or Reader).Affected if The version number falls within any of these ranges: 15.008.20082 through 21.007.20099, 17.011.30059 through 17.011.30204, 20.001.30005 through 20.004.30017, or 20.004.30017 and earlier.
-
Confirm the exact build numberLocate the full version string in the registry value or About dialog. It typically appears in format like 21.007.20099.xxxxxx. Note the first two numeric segments (major.minor) and the three-segment build (xx.xx.xxxxxx).Affected if The build number is 21.007.20099 or lower, 20.004.30017 or lower, 17.011.30204 or lower, or 15.008.20082 or higher within the affected ranges.
-
Determine if the application processes untrusted PDF filesReview whether users in the environment routinely open PDF attachments from unknown senders or download PDF files from untrusted websites. Check email gateway or endpoint protection policies for PDF handling restrictions.Affected if Users open PDF files from untrusted or unknown sources without prior validation, as the vulnerability is triggered by opening a maliciously crafted PDF.
You are affected if your installed Adobe Acrobat or Reader version falls within the specified version ranges AND users in your environment open PDF files from untrusted sources.
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 patched version and exercise caution when opening PDF files from untrusted sources.
For 21.x line: upgrade to version 21.008.x or later | For 20.x line: upgrade to version 20.005.x or later | For 17.x line: upgrade to version 17.012.x or later (or migrate to latest 21.x release)
- 1. Open Adobe Acrobat or Adobe Reader on your system
- 2. Navigate to Help > Check for Updates (or use the Help menu)
- 3. Allow the application to check for and download the latest version
- 4. Install the available security update
- 5. Alternatively, download the latest version from the official Adobe website: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 6. Restart the application after installation
- 7. Verify the version by going to Help > About Adobe Acrobat/Reader to confirm the version number
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-45068 — 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-45068 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