dbcve.org
Citrix Sd Wan CenterApplication · Citrix

CVE-2020-6175

MEDIUM · 5.9 CVSS v3.1 Published 2020-03-16
Fix available
A fix is available. Upgrade to 10.2.6 / 11.0.3 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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
Citrix SD-WAN 10.2.x before 10.2.6 and 11.0.x before 11.0.3 has Missing SSL Certificate Validation.

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 confidence

Citrix SD-WAN versions 10.2.x before 10.2.6 and 11.0.x before 11.0.3 fail to validate SSL certificates, allowing man-in-the-middle attackers to intercept encrypted traffic or inject malicious content by presenting an invalid or fraudulent certificate that the system will accept without verification.

MitigationUpgrade Citrix SD-WAN to version 10.2.6 or later, or 11.0.3 or later. If immediate upgrade is not possible, restrict network access to trusted endpoints and monitor for suspicious TLS/SSL traffic patterns.

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
Citrix Sd Wan CenterApplication
Affected:>= 10.1.1, <= 10.1.2>= 10.2.0, < 10.2.6>= 11.0.0, < 11.0.3
Netscaler Sd Wan CenterApplication
Affected:<= 10.0.8

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
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/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 checks

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

  1. Identify the installed Citrix SD-WAN Center version
    Access the SD-WAN Center web interface and navigate to the Administration or About section to view the exact version number. Alternatively, use the CLI command 'show version' or check the software package filename if accessible.
    Affected if The version falls within 10.1.1 to 10.1.2, 10.2.0 to 10.2.5, or 11.0.0 to 11.0.2 (for Citrix Sd Wan Center), or version 10.0.8 or earlier (for Citrix Netscaler Sd Wan Center).
  2. Confirm the specific product name in use
    Verify whether the deployment uses 'Citrix SD-WAN Center' or 'Citrix NetScaler SD-WAN Center' by checking the product name displayed in the web interface header or in the system documentation.
    Affected if Using NetScaler SD-WAN Center version 10.0.8 or lower.
  3. Check SSL certificate verification settings
    Review the SSL/TLS configuration in the SD-WAN Center settings under Network > SSL Settings or similar. Look for options controlling certificate validation such as 'Verify Peer Certificate', 'Validate Server Certificate', or SSL inspection-related configurations.
    Affected if SSL certificate validation is disabled, set to optional, or the configuration explicitly allows invalid certificates.
  4. Review SSL inspection or decryption configurations
    Examine any SSL inspection, decryption, or proxy-related configurations in the SD-WAN interface. Check if a custom CA certificate is installed for traffic inspection purposes.
    Affected if SSL inspection is enabled and a custom CA is configured without proper certificate validation controls.

A user is affected if their Citrix SD-WAN Center version is 10.1.1-10.1.2, 10.2.0-10.2.5, 11.0.0-11.0.2, or NetScaler SD-WAN Center version 10.0.8 or earlier, OR if SSL certificate validation is explicitly disabled in the configuration.

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 10.2.6 / 11.0.3 or later
Fixed in 10.2.611.0.3
Interim mitigation

Upgrade Citrix SD-WAN to version 10.2.6 or later, or 11.0.3 or later. If immediate upgrade is not possible, restrict network access to trusted endpoints and monitor for suspicious TLS/SSL traffic patterns.

Fix this in Citrix Sd Wan Center Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-6175 — 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-6175 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