CVE-2020-9593
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.20042 and earlier, 2017.011.30166 and earlier, 2017.011.30166 and earlier, and 2015.006.30518 and earlier have an invalid memory access vulnerability. Successful exploitation could lead to information disclosure.
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 confidenceThis is an invalid memory access vulnerability in Adobe Acrobat and Reader affecting multiple older version branches (2020.x, 2017.x, and 2015.x). The vulnerability can be exploited to read memory contents, leading to information disclosure.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 DC or Reader DC is installedOn Windows, open Programs and Features or check the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\ for entries containing 'Adobe Acrobat' or 'Adobe Reader'. On macOS, check /Applications for Adobe Acrobat or Adobe Reader.Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
-
Identify the exact installed versionOn Windows, run 'reg query "HKLM\SOFTWARE\Adobe\Adobe Acrobat\DC\InstallProperties" /v Version' or right-click the executable, select Properties, and check the Details tab. On macOS, right-click the app in Applications, select Get Info, and note the Version field.Affected if The version number cannot be determined or retrieved
-
Compare version against affected ranges for 15.x branchCheck if the installed version falls between 15.006.30060 and 15.006.30518 (inclusive of lower, exclusive of upper), or between 15.008.20082 and 20.006.20042 (inclusive of lower, exclusive of upper). Example: version 15.006.30400 is vulnerable; version 15.006.30518 or later is not.Affected if Version starts with 15.006.30060 or higher but is below 15.006.30518, OR is 15.008.20082 or higher but below 20.006.20042
-
Compare version against affected ranges for 17.x branchCheck if the installed version falls between 17.011.30059 and 17.011.30166 (inclusive of lower, exclusive of upper). Example: version 17.011.30100 is vulnerable; version 17.011.30166 or later is not.Affected if Version starts with 17.011.30059 or higher but is below 17.011.30166
-
Confirm vulnerability applies only when the product is actively usedThis memory disclosure flaw requires opening a malicious PDF file. Check whether the application is used to open PDF documents from untrusted sources.Affected if The user opens PDF documents in Adobe Acrobat or Reader
The system is affected if Adobe Acrobat DC or Adobe Acrobat Reader DC is installed with a version matching any of the three vulnerable ranges: 15.006.30060 to 15.006.30518, 15.008.20082 to 20.006.20042, or 17.011.30059 to 17.011.30166.
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.
From vendor data15.006.3051817.011.3016620.006.20042
Update Adobe Acrobat and Reader to the latest patched versions provided by Adobe's security updates.
- 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-2020-9593 — 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-9593 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