dbcve.org
Netscaler Sd WanApplication · Citrix

CVE-2018-17446

CRITICAL · 9.8 CVSS v3.0 Published 2018-10-23
Fix available
A fix is available. Upgrade to after 10.0.4 or later.
See remediation →
100/100
Remediation priority · Urgent
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
A SQL Injection issue was discovered in Citrix SD-WAN 10.1.0 and NetScaler SD-WAN 9.3.x before 9.3.6 and 10.0.x before 10.0.4.

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

SQL injection vulnerability in Citrix SD-WAN (NetScaler SD-WAN) allows remote attackers to execute arbitrary SQL commands via unsanitized input in web interface parameters, potentially leading to unauthorized database access, data exfiltration, or compromise of the SD-WAN appliance.

MitigationApply vendor patches: upgrade to SD-WAN 9.3.6 or 10.0.4 or later. Until patched, restrict network access to the management interface and implement WAF rules to filter SQL injection payloads.

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 Sd WanApplication
Affected:>= 9.3.0, <= 9.3.6>= 10.0.0, <= 10.0.4
Sd WanApplication
Affected:= 10.1.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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

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

  1. Identify installed SD-WAN version
    Log into the SD-WAN web management interface and navigate to the Dashboard or System > Diagnostics > View Version. Alternatively, use the CLI command 'show version' or 'system -show' to retrieve the firmware version.
    Affected if The displayed version falls within 9.3.0-9.3.6, 10.0.0-10.0.4, or exactly 10.1.0.
  2. Confirm web interface is enabled
    Access the SD-WAN appliance via CLI or web interface and verify the HTTP/HTTPS management service status. In the web UI, check under Configuration > System > Management Interface or similar path. In CLI, use commands like 'show http' or 'show managementinterface'.
    Affected if The web management interface is enabled and operational.
  3. Verify network accessibility of management interface
    From an external or non-management network segment, attempt to reach the SD-WAN management IP on ports 80/443 (HTTP/HTTPS). Use a tool like curl or telnet: curl -k https://<management-ip>/ or telnet <management-ip> 443.
    Affected if The management web interface is reachable from untrusted networks, indicating exposure to the SQL injection vector.
  4. Check for recent authentication logs
    Review the SD-WAN logs for suspicious SQL injection patterns in web requests. Access logs via the web interface under Monitoring > Logs > Access Logs, or export logs via CLI using 'export logs' or similar commands.

You are affected if your SD-WAN version is 9.3.0 through 9.3.6, 10.0.0 through 10.0.4, or exactly 10.1.0, AND the web management interface is exposed to network segments where untrusted users could send requests.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 10.0.4
Interim mitigation

Apply vendor patches: upgrade to SD-WAN 9.3.6 or 10.0.4 or later. Until patched, restrict network access to the management interface and implement WAF rules to filter SQL injection payloads.

Recommended fix High confidence

Upgrade to 9.3.6 (for 9.3.x branch), 10.0.4 (for 10.0.x branch), or next available 10.1.x release after 10.1.0

  1. 1. Identify the current Citrix SD-WAN / NetScaler SD-WAN version by logging into the SD-WAN web interface or checking via CLI
  2. 2. Determine which version branch you are running (9.3.x, 10.0.x, or 10.1.0)
  3. 3. For 9.3.x versions: Upgrade to version 9.3.6 which contains the security fix
  4. 4. For 10.0.x versions: Upgrade to version 10.0.4 which contains the security fix
  5. 5. For version 10.1.0: Upgrade to the next available patched release (10.1.x subsequent version)
  6. 6. After upgrade, verify the installed version matches the fixed release
  7. 7. Test that the SQL injection vulnerability is remediated
Caveat Review Citrix release notes for any configuration or behavioral changes between your current version and the target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Netscaler Sd Wan Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,320
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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