dbcve.org
Acrobat DcApplication · Adobe

CVE-2020-9595

MEDIUM · 5.5 CVSS v3.1 Published 2020-06-25
Fix available
A fix is available. Upgrade to 15.006.30518 / 17.011.30166 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
Adobe 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 · moderate confidence

This is an invalid memory access vulnerability in Adobe Acrobat and Reader affecting multiple version branches (2020.x, 2017.x, and 2015.x). The flaw allows attackers to read sensitive information from memory due to improper memory handling during PDF document processing.

MitigationUpdate Adobe Acrobat and Reader to the latest patched versions beyond 2020.006.20042, 2017.011.30166, and 2015.006.30518. Deploy via enterprise patch management and verify completion across all endpoints.

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
Acrobat DcApplication
Affected:>= 15.006.30060, < 15.006.30518>= 15.008.20082, < 20.006.20042>= 17.011.30059, < 17.011.30166
Acrobat Reader DcApplication
Affected:>= 15.006.30060, < 15.006.30518>= 15.008.20082, < 20.006.20042>= 17.011.30059, < 17.011.30166

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Verify Adobe Acrobat DC or Reader DC is installed
    Check Windows registry under HKLM\SOFTWARE\Adobe\Acrobat DC or HKLM\SOFTWARE\Adobe\Acrobat Reader DC for the InstallPath value, or look for the application in Program Files
    Affected if Either Adobe Acrobat DC or Adobe Acrobat Reader DC is present on the system
  2. Obtain the installed product version
    Check the Windows registry value Version at HKLM\SOFTWARE\Adobe\Acrobat DC\(version) or HKLM\SOFTWARE\Adobe\Acrobat Reader DC\(version), or open the application and navigate to Help > About Adobe Acrobat DC/Reader DC
    Affected if Unable to retrieve a version number indicates the product may not be properly installed or is a different edition
  3. Compare against affected version range 15.006.30060 to 15.006.30518
    Take the installed version and check if it falls in the range: major.minor.build.subbuild format (e.g., 15.006.30404 falls within this range)
    Affected if Version is 15.006.30060 or higher but lower than 15.006.30518
  4. Compare against affected version range 15.008.20082 to 20.006.20042
    Take the installed version and check if it falls in the range: major.minor.build.subbuild format (e.g., 17.011.30059 falls within this range)
    Affected if Version is 15.008.20082 or higher but lower than 20.006.20042
  5. Compare against affected version range 17.011.30059 to 17.011.30166
    Take the installed version and check if it falls in the range: major.minor.build.subbuild format (e.g., 17.011.30100 falls within this range)
    Affected if Version is 17.011.30059 or higher but lower than 17.011.30166

If Adobe Acrobat DC or Reader DC is installed and the version matches any of the three affected ranges (15.006.30060-15.006.30518, 15.008.20082-20.006.20042, or 17.011.30059-17.011.30166), the environment is vulnerable to CVE-2020-9595.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to 15.006.30518 / 17.011.30166 / 20.006.20042 or later
Fixed in 15.006.3051817.011.3016620.006.20042
Interim mitigation

Update Adobe Acrobat and Reader to the latest patched versions beyond 2020.006.20042, 2017.011.30166, and 2015.006.30518. Deploy via enterprise patch management and verify completion across all endpoints.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-9595 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-9595 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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