CVE-2020-3793
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 confidenceUse-after-free vulnerability in Adobe Acrobat and Reader allowing arbitrary code execution via maliciously crafted PDF files. The vulnerability exists in versions 2020.006.20034 and earlier, 2017.011.30158 and earlier, and 2015.006.30510 and earlier.
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.
-
Verify Adobe Acrobat or Reader installationCheck Add/Remove Programs (Windows) or Applications folder (Mac) for Adobe Acrobat DC or Adobe Acrobat Reader DCAffected if Either product is present on the system
-
Find the exact version numberOpen the application, go to Help > About Adobe Acrobat/Reader, or on Windows run: wmic product where "name like 'Adobe Acrobat%'" get versionAffected if Version cannot be determined or is older than the listed affected versions
-
Compare against first affected range (15.006.30060 to 15.006.30517)Check if your version starts with 15.006 and falls between 15.006.30060 and 15.006.30517 inclusiveAffected if Version matches this pattern and is less than 15.006.30518
-
Compare against second affected range (15.008.20082 to 20.006.20041)Check if your version starts with 15.008 or 20.006 and falls between 15.008.20082 and 20.006.20041 inclusiveAffected if Version matches this pattern and is less than 20.006.20042
-
Compare against third affected range (17.011.30059 to 17.011.30165)Check if your version starts with 17.011 and falls between 17.011.30059 and 17.011.30165 inclusiveAffected if Version matches this pattern and is less than 17.011.30166
The system is affected if Adobe Acrobat DC or Reader DC is installed and the version falls within any of the three vulnerable ranges: 15.006.30060-15.006.30517, 15.008.20082-20.006.20041, or 17.011.30059-17.011.30165.
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
Apply Adobe security patches (2020.006.20042, 2017.011.30166, and 2015.006.30518 or later) to all affected Acrobat and Reader installations; prioritize internet-facing and frequently-used systems given the critical severity.
Acrobat DC/Reader DC version 15.006.30518, 20.006.20042, or 17.011.30166 (or later corresponding to your release track)
- Identify the currently installed Adobe Acrobat or Acrobat Reader version via Help > About Adobe Acrobat/Reader
- For versions 15.006.30060 through 15.006.30517, upgrade to version 15.006.30518 or later
- For versions 15.008.20082 through 20.006.20041, upgrade to version 20.006.20042 or later
- For versions 17.011.30059 through 17.011.30165, upgrade to version 17.011.30166 or later
- Download the latest version from the Adobe Acrobat download page 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
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3793 — 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-3793 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