CVE-2015-1460
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 · uneditedHuawei Quidway switches with firmware before V200R005C00SPC300 allows remote attackers to gain privileges via a crafted packet.
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 confidenceHuawei Quidway switches running firmware versions prior to V200R005C00SPC300 contain a privilege escalation vulnerability that allows remote attackers to gain elevated privileges by sending specially crafted packets to the device.
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<= 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
- Low
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Confirm device is a Huawei Quidway switchIdentify the device model by checking the physical hardware label, SNMP sysDescr, or console boot messages. The vulnerability applies specifically to Huawei Quidway switch models.Affected if The device is not a Huawei Quidway switch (this CVE does not apply)
-
Retrieve the installed firmware versionAccess the device console or management interface and run the command to display the version, such as 'display version' or 'display device version'. Alternatively, check via SNMP or the web management interface if available.Affected if Unable to retrieve the firmware version for comparison
-
Compare firmware version against affected rangeReview the displayed firmware version and compare it to the affected range: any version <= v200r003c00spc300 is vulnerable. Versions prior to V200R005C00SPC300 are affected; V200R005C00SPC300 and later are fixed.Affected if The installed version is v200r003c00spc300 or any earlier version
-
Assess network exposure of management interfacesCheck the device network configuration to determine if management interfaces (console, telnet, SSH, web UI) are reachable from untrusted networks. Review ACLs, VLAN assignments, and interface IP addresses.Affected if Management interfaces are exposed to untrusted networks (the vulnerability is remotely exploitable)
You are affected if the device is a Huawei Quidway switch running firmware version v200r003c00spc300 or any earlier version, and management interfaces are network-accessible to potential attackers.
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 dataUpgrade affected Huawei Quidway switches to firmware version V200R005C00SPC300 or later. If immediate patching is not possible, restrict network access to management interfaces and monitor for anomalous packet patterns.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-1460 — 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-2015-1460 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