CVE-2019-9160
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 · uneditedWAC on the Sangfor Sundray WLAN Controller version 3.7.4.2 and earlier has a backdoor account allowing a remote attacker to login to the system via SSH (on TCP port 22345) and escalate to root (because the password for root is the WebUI admin password concatenated with a static string).
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 confidenceThe Sangfor Sundray WLAN Controller versions 3.7.4.2 and earlier contain a hardcoded backdoor account accessible via SSH on TCP port 22345. An attacker with network access to this port can authenticate using the backdoor credentials and escalate to root privileges by using the WebUI admin password concatenated with a static string.
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<= 3.7.4.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify if TCP port 22345 is openScan the target device for open ports, specifically check if TCP port 22345 is listening. Use nmap -p 22345 <target> or netstat/ss commands to list listening ports.Affected if TCP port 22345 is accessible and accepting connections indicates the backdoor SSH service may be running
-
Confirm the device is a Sangfor Sundray WLAN ControllerIdentify the device through SSH bannergrabbing on port 22345, or check the web UI if accessible, or review network documentation to determine if the device is a Sangfor Sundray or Xinruidz Sundray WLAN Controller.Affected if The device is a Sangfor Sundray or Xinruidz Sundray WLAN Controller and port 22345 is exposed
-
Check the firmware versionAccess the device management interface (web UI or console) and locate the firmware version information, typically found in System Settings or About pages. Compare the installed version against the affected range.Affected if The firmware version is 3.7.4.2 or earlier
-
Verify SSH access on port 22345Attempt to establish an SSH connection to the device on port 22345. If a connection is successful, observe the login prompt to confirm the service is accessible.Affected if SSH service is reachable on port 22345, confirming the backdoor attack surface exists
A user is affected if they have a Sangfor Sundray WLAN Controller with firmware version 3.7.4.2 or earlier that exposes TCP port 22345 to the network.
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 dataRestrict network access to port 22345 immediately via firewall rules or network segmentation. Contact Sangfor for available firmware updates that address this backdoor vulnerability.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-9160 — 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-2019-9160 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