CVE-2020-8195
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 · uneditedImproper input validation in Citrix ADC and Citrix Gateway versions before 13.0-58.30, 12.1-57.18, 12.0-63.21, 11.1-64.14 and 10.5-70.18 and Citrix SDWAN WAN-OP versions before 11.1.1a, 11.0.3d and 10.2.7 resulting in limited information disclosure to low privileged users.
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 confidenceImproper input validation in Citrix ADC and Citrix Gateway and SDWAN WAN-OP allows authenticated low-privileged users to access limited information they should not be able to view. This is an access control bypass via crafted input rather than a direct injection flaw.
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>= 10.5, < 10.5-70.18>= 11.1, < 11.1-64.14>= 12.0, < 12.0-63.21>= 12.1, < 12.1-57.18>= 13.0, < 13.0-58.30>= 10.5, < 10.5-70.18>= 11.1, < 11.1-64.14>= 12.0, < 12.0-63.21>= 12.1, < 12.1-57.18>= 13.0, < 13.0-58.30>= 10.2, < 10.2.7>= 11.0, < 11.0.3d>= 11.1, < 11.1.1a< 1.0.0.137CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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.
-
Identify Citrix ADC or Gateway firmware versionRun 'show version' via NSCLI or check the management GUI under System > Information > VersionAffected if The version falls within any of these ranges: 10.5 to 10.5-70.17, 11.1 to 11.1-64.13, 12.0 to 12.0-63.20, 12.1 to 12.1-57.17, or 13.0 to 13.0-58.29
-
Identify Citrix SDWAN WAN-OP firmware versionRun 'show system info' via WAN-OP CLI or check the web interface under Administration > System InformationAffected if The version falls within: 10.2 to 10.2.6, 11.0 to 11.0.3c, or 11.1 to 11.1.1
-
Identify Citrix Gateway Plug-in for Linux versionCheck the installed package version using 'dpkg -l | grep citrix' or 'rpm -qa | grep citrix' on Linux clientsAffected if The version is earlier than 1.0.0.137
-
Verify presence of low-privilege user accountsList user accounts via 'show system user' in ADC/Gateway CLI or check Configuration > User Administration > Users in the GUIAffected if Any non-administrator user accounts exist in the system
-
Confirm web management interface exposureCheck if the Citrix ADC/Gateway management GUI (ports 80/443 or UI) is accessible from untrusted networks or verify the ns.conf for 'set ns mode' configurationsAffected if The management interface is reachable by authenticated low-privilege users
You are affected if your Citrix ADC, Gateway, or SDWAN WAN-OP firmware version is within the vulnerable ranges listed AND low-privileged user accounts have access to the management interface.
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 · scoped1.0.0.13710.2.710.5-70.18
Upgrade Citrix ADC/Gateway to versions 13.0-58.30, 12.1-57.18, 12.0-63.21, 11.1-64.14, or 10.5-70.18 or later; upgrade SDWAN WAN-OP to 11.1.1a, 11.0.3d, 10.2.7 or later. Alternatively, restrict low-privilege user access until patches can be applied.
Citrix ADC/Gateway: 10.5-70.18, 11.1-64.14, 12.0-63.21, 12.1-57.18, or 13.0-58.30 (depending on your current branch); SD-WAN: 11.1.1a, 11.0.3d, or 10.2.7; Gateway Plug In For Linux: 1.0.0.137
- 1. Identify the exact Citrix product, model, and current firmware version by navigating to the System > Information > Diagnostics section in the management GUI or running 'show version' via CLI
- 2. Determine the appropriate target firmware version based on your current branch: for 10.5.x upgrade to 10.5-70.18; for 11.1.x upgrade to 11.1-64.14; for 12.0.x upgrade to 12.0-63.21; for 12.1.x upgrade to 12.1-57.18; for 13.0.x upgrade to 13.0-58.30; for SD-WAN upgrade to 11.1.1a (or 11.0.3d or 10.2.7 as applicable); for Gateway Plug In For Linux upgrade to 1.0.0.137
- 3. Create a full configuration backup by navigating to System > Backup and Restore > Create Backup in the GUI or using 'save ns config' via CLI
- 4. Review Citrix upgrade documentation and release notes for your specific model to verify compatibility and required pre-upgrade steps
- 5. Download the appropriate firmware build from the Citrix support portal (support.citrix.com) - you will need a valid Citrix account
- 6. Upload the firmware file through System > Firmware > Upload in the GUI or via SCP/TFTP
- 7. Install the firmware by selecting the uploaded build and clicking Install, or via CLI using 'install firmware <build-number>'
- 8. Reboot the device when prompted or using 'reboot' command after installation completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8195 — 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-8195 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