dbcve.org
Netscaler Sdx FirmwareOperating system · Citrix

CVE-2013-3620

HIGH · 7.5 CVSS v3.1 Published 2020-01-02
Fix available
A fix is available. Upgrade to 3.12 / 3.15 or later.
See remediation →
84/100
Remediation priority · High
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
Hardcoded WSMan credentials in Intelligent Platform Management Interface (IPMI) with firmware for Supermicro X9 generation motherboards before 3.15 (SMT_X9_315) and firmware for Supermicro X8 generation motherboards before SMT X8 312.

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

Hardcoded WSMan credentials exist in the Intelligent Platform Management Interface (IPMI) firmware of Supermicro X9 generation motherboards before version 3.15 (SMT_X9_315) and X8 generation motherboards before SMT X8 312. These static credentials allow remote attackers to bypass authentication and gain unauthorized access to the IPMI management interface.

MitigationUpdate IPMI firmware to SMT_X9_315 or later for X9 motherboards, and SMT X8 312 or later for X8 motherboards. If firmware updates are not feasible, isolate IPMI interfaces on a restricted network segment and disable remote WSMan access.

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 Sdx FirmwareOperating system
Affected:= 10
Netscaler FirmwareOperating system
Affected:all versions
Netscaler Sd Wan FirmwareOperating system
Affected:all versions
Smt X9 FirmwareOperating system
Affected:< 3.15
Smt X8 FirmwareOperating system
Affected:< 3.12

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/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 the hardware platform
    Determine if the target system is a Supermicro X8 or X9 generation motherboard, or a Citrix Netscaler (SDX, standard, or SD-WAN) appliance. Check system inventory, BIOS information, or physically label the server.
    Affected if The system is a Supermicro X8/X9 motherboard or any Citrix Netscaler variant.
  2. Check Supermicro IPMI firmware version
    Access the IPMI web interface or use IPMI utilities (ipmitool) to query the firmware version. Command example: 'ipmitool -I lanplus -H <IPMI_IP> -U ADMIN -P ADMIN fru print' or check the BMC firmware version through the web UI under 'Maintenance' or 'Firmware Update'.
    Affected if The IPMI firmware version is below 3.15 for X9 motherboards or below 3.12 for X8 motherboards.
  3. Confirm Citrix Netscaler variant and version
    For Citrix Netscaler systems, run 'show version' in the CLI or check the web UI under 'System' > 'Diagnostics' > 'Show Version'. Identify whether it is SDX, standard, or SD-WAN model.
    Affected if Any Citrix Netscaler SDX firmware version 10, or any version of Citrix Netscaler standard or SD-WAN firmware, is affected.
  4. Verify if WSMan remote access is enabled
    Check the IPMI/BMC configuration for WSMan (Windows Remote Management) settings. In the Supermicro IPMI web UI, go to 'Settings' > 'Services' or 'Remote Management' and look for WSMan or remote IPMI over HTTP/HTTPS services. Use ipmitool: 'ipmitool -I lanplus -H <IPMI_IP> -U ADMIN -P ADMIN raw 0x32 0x76 0x01 0x00' or check BMC network services.
    Affected if WSMan or remote IPMI management interfaces are enabled and accessible over the network.
  5. Check IPMI network accessibility
    Ping the IPMI/BMC IP address and attempt to connect to ports 623 (UDP - IPMI), 443 (HTTPS - web UI), or 5985/5986 (WinRM/WSMan). Use 'nmap -sU -p 623 <IPMI_IP>' to verify IPMI is exposed.
    Affected if The IPMI interface is reachable from untrusted networks, indicating potential exposure to remote attackers.

A system is affected if it is a Supermicro X8/X9 motherboard with IPMI firmware below 3.15/3.12, or any Citrix Netscaler (SDX, SD-WAN, or standard), and the IPMI/WSMan interface is network-accessible.

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
Upgrade available Upgrade to 3.12 / 3.15 or later
Fixed in 3.123.15
Interim mitigation

Update IPMI firmware to SMT_X9_315 or later for X9 motherboards, and SMT X8 312 or later for X8 motherboards. If firmware updates are not feasible, isolate IPMI interfaces on a restricted network segment and disable remote WSMan access.

Fix this in Netscaler Sdx Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
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,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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