CVE-2020-8272
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 · uneditedAuthentication Bypass resulting in exposure of SD-WAN functionality in Citrix SD-WAN Center versions before 11.2.2, 11.1.2b and 10.2.8
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 confidenceAuthentication bypass vulnerability in Citrix SD-WAN Center allows unauthorized attackers to bypass authentication mechanisms and gain access to SD-WAN management functionality. The flaw exists in versions prior to 11.2.2, 11.1.2b, and 10.2.8, potentially exposing sensitive network configuration and operational controls.
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.2.0, < 10.2.8>= 11.1.0, < 11.1.2b>= 11.2.0, < 11.2.2CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 installed Citrix SD-WAN Center versionAccess the SD-WAN Center web interface and navigate to the About or System Information page to view the software version, or use the CLI command 'show version' if availableAffected if The version falls within any of these ranges: >= 10.2.0 and < 10.2.8, OR >= 11.1.0 and < 11.1.2b, OR >= 11.2.0 and < 11.2.2
-
Confirm management interface accessibilityDetermine if the SD-WAN Center management interface (typically on port 443 or 8443) is reachable from untrusted networks by checking firewall rules or attempting external accessAffected if The management interface is exposed to the internet or untrusted internal networks without VPN or IP restrictions
-
Verify authentication configurationCheck the SD-WAN Center authentication settings through the web UI under Administration or Security settings to confirm whether local authentication, LDAP, or RADIUS is configuredAffected if Authentication is enabled but the version is vulnerable, indicating the bypass flaw may be present
-
Review access logs for anomalous authentication patternsExamine SD-WAN Center logs for failed login attempts, especially unusual access patterns or requests to authentication endpoints that may indicate bypass attemptsAffected if Unusual authentication patterns are found, particularly requests that succeeded without proper credential validation
You are affected if your Citrix SD-WAN Center version is 10.2.0 through 10.2.7, 11.1.0 through 11.1.2a, or 11.2.0 through 11.2.1 and the management interface is accessible to potential 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.
From vendor data10.2.811.1.2b11.2.2
Upgrade Citrix SD-WAN Center to version 11.2.2, 11.1.2b, or 10.2.8 or later to remediate the authentication bypass. If immediate patching is not possible, restrict network access to the management interface via firewall rules or VPN.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8272 — 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-8272 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