CVE-2020-8193
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 access control 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 allows unauthenticated access to certain URL endpoints.
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 access control in Citrix ADC, Citrix Gateway, and Citrix SDWAN WAN-OP allows unauthenticated attackers to access certain URL endpoints that should require authentication. This is an authentication bypass vulnerability affecting specific version ranges of all three products.
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.1aCVSS 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
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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 the installed Citrix productAccess the management interface or CLI and determine whether the system is Citrix ADC, Citrix Gateway, or Citrix SDWAN WAN-OP. Check the product name displayed in the system information or welcome page.Affected if The product is Citrix ADC, Citrix Gateway, or Citrix SDWAN WAN-OP.
-
Determine the firmware versionLocate the firmware version in the system management interface, CLI (such as 'show version' or similar command), or the about/status page. Note the full version string including any build numbers.Affected if The installed version cannot be determined or is not visible.
-
Compare the version against affected ranges for ADC/GatewayIf the product is Citrix ADC or Citrix Gateway, compare the installed version to the vulnerable 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.Affected if The version falls within any of these ranges.
-
Compare the version against affected ranges for SDWANIf the product is Citrix SDWAN WAN-OP, compare the installed version to the vulnerable ranges: 10.2 to 10.2.6, 11.0 to 11.0.3c, or 11.1 to 11.1.1a (or the build before 11.1.1a).Affected if The version falls within any of these ranges.
-
Verify management interface exposureDetermine whether the Citrix management interface (nsgui, netscaler gateway, or SDWAN management ports) is accessible from untrusted networks. Check firewall rules, ACLs, or network segmentation configurations that control access to port 443/TCP on the appliance.Affected if The management interface is exposed to the internet or untrusted networks without additional access controls.
The system is affected if it runs Citrix ADC, Citrix Gateway, or Citrix SDWAN WAN-OP firmware with a version that falls within the vulnerable ranges AND the management interface is network-accessible to attackers.
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 · scoped10.2.710.5-70.1811.0.3d
Upgrade Citrix ADC and 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 Citrix SDWAN WAN-OP to versions 11.1.1a, 11.0.3d, 10.2.7 or later.
Upgrade to Citrix ADC/Gateway firmware 10.5-70.18, 11.1-64.14, 12.0-63.21, 12.1-57.18, or 13.0-58.30 (as appropriate for your product line); or SD-WAN WAN-OP firmware 10.2.7, 11.0.3d, or 11.1.1a
- 1. Identify the exact Citrix product (ADC, Gateway, or SD-WAN WAN-OP) and current firmware version running in the environment
- 2. Determine the appropriate fixed version based on the product type and current major version line
- 3. Back up the current configuration and any necessary data before proceeding
- 4. Download the fixed firmware version from Citrix Support (support.citrix.com) - ensure it matches your product model
- 5. Schedule a maintenance window as upgrades may require brief downtime
- 6. Apply the firmware upgrade following Citrix's standard upgrade procedure for the specific product
- 7. After upgrade completes, verify the system is operational and services are functioning
- 8. Confirm the new firmware version matches the fixed release (e.g., 10.5-70.18, 11.1-64.14, 12.0-63.21, 12.1-57.18, or 13.0-58.30 for ADC/Gateway; 10.2.7, 11.0.3d, or 11.1.1a for SD-WAN)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.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 $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8193 — 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-8193 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