CVE-2020-8246
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 · uneditedCitrix ADC and Citrix Gateway 13.0 before 13.0-64.35, Citrix ADC and NetScaler Gateway 12.1 before 12.1-58.15, Citrix ADC 12.1-FIPS before 12.1-55.187, Citrix ADC and NetScaler Gateway 12.0, Citrix ADC and NetScaler Gateway 11.1 before 11.1-65.12, Citrix SD-WAN WANOP 11.2 before 11.2.1a, Citrix SD-WAN WANOP 11.1 before 11.1.2a, Citrix SD-WAN WANOP 11.0 before 11.0.3f, Citrix SD-WAN WANOP 10.2 before 10.2.7b are vulnerable to a denial of service attack originating from the management network.
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 confidenceCitrix ADC, Citrix Gateway, NetScaler Gateway, and Citrix SD-WAN WANOP devices contain a denial of service vulnerability that can be exploited from the management network. An unauthenticated attacker on the management network can send specially crafted requests to trigger the DoS condition, causing the affected device to become unresponsive or crash.
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>= 11.1, < 11.1-65.12>= 12.1, < 12.1-58.15>= 13.0, < 13.0-64.35>= 11.1, < 11.1-65.12>= 13.0, < 13.0-64.35>= 12.1, < 12.1-58.15>= 10.2, < 10.2.7b>= 11.0, < 11.0.3f>= 11.1, < 11.1.2a>= 11.2, < 11.2.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 product and firmware versionLog into the device CLI and run 'show version' or 'nsversion' command, or access the web interface System Information page under DiagnosticsAffected if The version shown falls within any of these ranges: Citrix ADC/Gateway 11.1 before 11.1-65.12, 12.1 before 12.1-58.15, or 13.0 before 13.0-64.35; SD-WAN WANOP 10.2 before 10.2.7b, 11.0 before 11.0.3f, 11.1 before 11.1.2a, or 11.2 before 11.2.1a
-
Confirm the specific Citrix product variantRun 'show hardware' or check the web interface license information to determine if the device is running as Citrix ADC, Citrix Gateway, NetScaler Gateway, or SD-WAN WANOPAffected if The device is any of these products and the version from step 1 matches the affected ranges for that specific product
-
Verify management interface exposureCheck network configuration via 'show ip' or the web interface under Network > IP Addresses. Determine if the management interface (typically IP with nsip, nsip6, or management IP) is reachable from untrusted networksAffected if The management interface IP is accessible from networks beyond trusted administration staff
-
Check device availability and crash indicatorsRun 'show system' or 'show techsupport' and review recent system logs for unexpected restarts, core dumps, or periods of unresponsivenessAffected if The device shows signs of unexpected crashes or downtime that align with the timing of potential exploitation from the management network
You are affected if your Citrix ADC, Gateway, NetScaler Gateway, or SD-WAN WANOP device runs a firmware version listed in the affected ranges and has its management interface reachable from networks where untrusted attackers could send crafted requests.
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.7b11.0.3f11.1.2a
Apply the vendor-provided patches for the specific product version (13.0-64.35, 12.1-58.15, 11.1-65.12, or respective SD-WAN WANOP updates) and consider network segmentation to restrict management interface access to trusted networks only.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-8246 — 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-8246 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