CVE-2014-5394
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 · uneditedMultiple Huawei Campus switches allow remote attackers to enumerate usernames via vectors involving use of SSH by the maintenance terminal.
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 · moderate confidenceThis is a username enumeration vulnerability in Huawei Campus switches where remote attackers can discover valid usernames through the SSH maintenance terminal interface. By sending specially crafted SSH authentication requests, attackers can determine which usernames exist on the system, facilitating subsequent brute-force attacks.
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= v200r001c00spc300= v200r002c00spc300= v200r003c00spc500= v200r001c00spc300= v200r002c00spc300= v200r003c00spc500= v200r001c00spc300= v200r002c00spc300= v200r003c00spc500= v200r001c00spc300= v200r002c00spc300= v200r003c00spc500= v200r001c00spc300= v200r002c00spc300= v200r003c00spc300= v200r001c00spc300= v200r002c00spc300= v200r003c00spc300= v200r001c00spc300= v200r002c00spc300= v200r003c00spc300= v200r001c00spc300= v200r002c00spc300= v200r003c00spc300CVSS 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 device modelRun 'display device' or check hardware label to confirm the switch model is S9300, S9300e, S7700, S9700, S5700, S6700, S5300, or S6300Affected if Device is one of these models
-
Check firmware versionRun 'display version' to obtain the firmware version stringAffected if Version equals v200r001c00spc300, v200r002c00spc300, v200r003c00spc500, or v200r003c00spc300
-
Verify SSH maintenance terminal is accessibleConfirm that the SSH service on the maintenance terminal interface (typically VLAN 1 or management interface) is enabled and reachable from the networkAffected if SSH is enabled and accessible on the maintenance terminal
The device is affected if it is one of the listed Huawei switch models running one of the specified firmware versions and has SSH access enabled on the maintenance terminal.
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 SSH access to the maintenance terminal to trusted management networks via ACLs, implement rate limiting on SSH authentication attempts, and consider disabling password-based authentication in favor of certificate-based authentication.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2014-5394 — 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-2014-5394 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