CVE-2020-3805
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 · uneditedAdobe Acrobat and Reader versions 2020.006.20034 and earlier, 2017.011.30158 and earlier, 2017.011.30158 and earlier, 2015.006.30510 and earlier, and 2015.006.30510 and earlier have a use-after-free vulnerability. Successful exploitation could lead to arbitrary code execution .
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 confidenceA use-after-free vulnerability in Adobe Acrobat and Reader allows attackers to achieve arbitrary code execution by exploiting memory that is accessed after being freed. This memory corruption issue affects versions 2020.006.20034 and earlier, 2017.011.30158 and earlier, and 2015.006.30510 and earlier, with a critical CVSS score of 9.8 indicating straightforward exploitation and severe impact.
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.006.30060, < 15.006.30518>= 15.008.20082, < 20.006.20042>= 17.011.30059, < 17.011.30166>= 15.006.30060, < 15.006.30518>= 15.008.20082, < 20.006.20042>= 17.011.30059, < 17.011.30166CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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.
-
Check if Adobe Acrobat or Reader is installedOn Windows, open Registry Editor and navigate to HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ or check Add/Remove Programs. Look for entries containing 'Adobe Acrobat' or 'Adobe Reader'. On macOS, check /Applications folder for Adobe Acrobat or Adobe Reader apps.Affected if Neither Adobe Acrobat nor Adobe Reader is installed on the system
-
Determine the installed version of Adobe AcrobatRight-click the Adobe Acrobat shortcut or executable, select Properties, then look at the Details tab for the Product Version. Alternatively, open Acrobat and go to Help > About Adobe Acrobat.Affected if The displayed version matches one of the affected version ranges: 15.006.30060 to 15.006.30517, 15.008.20082 to 20.006.20041, or 17.011.30059 to 17.011.30165
-
Determine the installed version of Adobe ReaderOpen Adobe Reader, then go to Help > About Adobe Reader to view the product version.Affected if The displayed version matches one of the affected version ranges: 15.006.30060 to 15.006.30517, 15.008.20082 to 20.006.20041, or 17.011.30059 to 17.011.30165
-
Compare version against CVE-2020-3805 affected rangesCompare your installed version number to the affected ranges: 2020.006.20034 and earlier, 2017.011.30158 and earlier, or 2015.006.30510 and earlier.Affected if Your installed version is 2020.006.20034 or lower, 2017.011.30158 or lower, or 2015.006.30510 or lower
If Adobe Acrobat or Reader is installed and the version falls within any of the affected ranges (15.006.30060-15.006.30517, 15.008.20082-20.006.20041, or 17.011.30059-17.011.30165), your environment is affected by this use-after-free vulnerability.
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 · scoped15.006.3051817.011.3016620.006.20042
Upgrade Adobe Acrobat and Reader to the latest patched versions released in March 2020. Organizations should also implement endpoint protection and restrict opening of untrusted PDF files until patches are applied.
Adobe Acrobat/Reader DC 20.006.20042 (or later for Continuous track); 17.011.30166 (or later for Classic 2017); 15.006.30518 (or later for Classic 2015)
- Identify the currently installed Adobe Acrobat or Acrobat Reader version via Help > About Adobe Acrobat/Reader
- For Acrobat DC (Continuous track): Upgrade to version 20.006.20042 or later
- For Acrobat DC (Classic 2017 track): Upgrade to version 17.011.30166 or later
- For Acrobat DC (Classic 2015 track): Upgrade to version 15.006.30518 or later
- For Acrobat Reader DC: Apply the same version upgrades as Acrobat DC (Reader is included in the same release)
- Download the appropriate updated version from the official Adobe website or use the built-in Help > Check for Updates feature
- Restart the application after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3805 — 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-2020-3805 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