dbcve.org
Application Delivery Controller FirmwareOperating system · Citrix

CVE-2017-17382

MEDIUM · 5.9 CVSS v3.0 Published 2017-12-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 NetScaler Application Delivery Controller (ADC) and NetScaler Gateway 10.5 before build 67.13, 11.0 before build 71.22, 11.1 before build 56.19, and 12.0 before build 53.22 might allow remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a ROBOT attack.

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 NetScaler ADC and NetScaler Gateway contain a Bleichenbacher RSA padding oracle vulnerability (ROBOT attack variant) that allows remote attackers to decrypt TLS ciphertext by sending specially crafted RSA ciphertexts and analyzing timing differences in server error responses.

MitigationApply the vendor-released patches for the affected builds (67.13 for 10.5, 71.22 for 11.0, 56.19 for 11.1, 53.22 for 12.0) to address the padding oracle weakness in the TLS implementation.

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
Application Delivery Controller FirmwareOperating system
Affected:= 10.5= 11.0= 11.1= 12.0
Netscaler Gateway FirmwareOperating system
Affected:= 10.5= 11.0= 11.1= 12.0

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.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 checks

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

  1. Identify NetScaler firmware version
    Log into the NetScaler command line and run 'show version' or 'nsversion' to display the installed firmware build. Alternatively, check the Citrix ADC web interface under System > Information > Version.
    Affected if The displayed firmware version matches 10.5, 11.0, 11.1, or 12.0 (any build).
  2. Confirm NetScaler ADC or Gateway deployment
    Run 'show hardware' or check the web interface to confirm whether the device is deployed as Citrix Application Delivery Controller (ADC) or Citrix NetScaler Gateway.
    Affected if The device is running Citrix Application Delivery Controller Firmware or Citrix Netscaler Gateway Firmware versions 10.5, 11.0, 11.1, or 12.0.
  3. Check if SSL/TLS services are enabled
    Run 'show ssl service' or 'show ssl vserver' from the command line to list active SSL services and their configurations. Verify which TLS services are bound and active.
    Affected if SSL/TLS services (like SSL VPN, SSL ADC, or web interface over HTTPS) are enabled and actively listening.
  4. Verify RSA-based cipher suites are in use
    Run 'show ssl cipher' or inspect the SSL profile configuration via 'show ssl profile' to identify which cipher suites are configured. Look for RSA key exchange ciphers (such as TLS_RSA_*).
    Affected if RSA key exchange cipher suites are configured or permitted in the SSL profile or virtual server settings.

You are affected if your NetScaler ADC or Gateway firmware version is 10.5, 11.0, 11.1, or 12.0 AND RSA-based TLS services are enabled and exposed.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-released patches for the affected builds (67.13 for 10.5, 71.22 for 11.0, 56.19 for 11.1, 53.22 for 12.0) to address the padding oracle weakness in the TLS implementation.

Fix this in Application Delivery Controller Firmware Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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