Netscaler Application Delivery Controller FirmwareApplication · Citrix
CVE-2017-5933
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 NetScaler ADC and NetScaler Gateway 10.5 before Build 65.11, 11.0 before Build 69.12/69.123, and 11.1 before Build 51.21 randomly generates GCM nonces, which makes it marginally easier for remote attackers to obtain the GCM authentication key and spoof data by leveraging a reused nonce in a session and a "forbidden attack," a similar issue to CVE-2016-0270.
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 NetScaler ADC and Gateway incorrectly generates GCM (Galois/Counter Mode) nonces with insufficient randomness, causing nonce reuse within sessions. This cryptographic weakness allows attackers to perform 'forbidden attacks' that can recover the GCM authentication key and potentially spoof data, similar to CVE-2016-0270.
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
Netscaler Application Delivery Controller FirmwareApplication
<= 10.5.65.11<= 11.0.69.12<= 11.1.51.21CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify NetScaler firmware versionLog into the NetScaler CLI and run 'show version' or 'show ns version' to display the exact build number and firmware versionAffected if The displayed build number is 10.5.65.11 or lower, 11.0.69.12 or lower, or 11.1.51.21 or lower
-
Confirm the affected firmware release lineExamine the major version number from the version output (10.5, 11.0, or 11.1) to determine which vulnerable range appliesAffected if Running any of the three affected version lines at a build at or below the corresponding threshold
-
Verify GCM cipher usage (optional context)Check SSL profile or virtual server configuration using 'show ssl vserver <name>' or 'show ssl profile <name>' and look for GCM-based cipher suites (such as TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384)Affected if GCM cipher suites are enabled - the nonce reuse flaw affects any GCM-encrypted sessions when using a vulnerable build
You are affected if your NetScaler ADC or Gateway is running firmware build 10.5.65.11 or lower, 11.0.69.12 or lower, or 11.1.51.21 or lower, regardless of GCM cipher configuration.
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 dataApply vendor-supplied patches: Build 65.11 for version 10.5, Build 69.12/69.123 for 11.0, or Build 51.21 for 11.1. Ensure proper testing in non-production environment before deployment due to the cryptographic nature of the fix.
Fix this in Netscaler Application Delivery Controller Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-5933 — 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-2017-5933 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