dbcve.org
Tecal Rh1288 V2 FirmwareOperating system · Huawei

CVE-2014-9692

HIGH · 7.5 CVSS v3.0 Published 2017-04-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Huawei Tecal RH1288 V2 V100R002C00SPC107 and earlier versions, Tecal RH2265 V2 V100R002C00, Tecal RH2285 V2 V100R002C00SPC115 and earlier versions, Tecal RH2265 V2 V100R002C00, Tecal RH2285H V2 V100R002C00SPC111 and earlier versions, Tecal RH2268 V2 V100R002C00, Tecal RH2288 V2 V100R002C00SPC117 and earlier versions, Tecal RH2288H V2 V100R002C00SPC115 and earlier versions, Tecal RH2485 V2 V100R002C00SPC502 and earlier versions, Tecal RH5885 V2 V100R001C02SPC109 and earlier versions, Tecal RH5885 V3 V100R003C01SPC102 and earlier versions, Tecal RH5885H V3 V100R003C00SPC102 and earlier versions, Tecal XH310 V2 V100R001C00SPC110 and earlier versions, Tecal XH311 V2 V100R001C00SPC110 and earlier versions, Tecal XH320 V2 V100R001C00SPC110 and earlier versions, Tecal XH621 V2 V100R001C00SPC106 and earlier versions, Tecal DH310 V2 V100R001C00SPC110 and earlier versions, Tecal DH320 V2 V100R001C00SPC106 and earlier versions, Tecal DH620 V2 V100R001C00SPC106 and earlier versions, Tecal DH621 V2 V100R001C00SPC107 and earlier versions, Tecal DH628 V2 V100R001C00SPC107 and earlier versions, Tecal BH620 V2 V100R002C00SPC107 and earlier versions, Tecal BH621 V2 V100R002C00SPC106 and earlier versions, Tecal BH622 V2 V100R002C00SPC110 and earlier versions, Tecal BH640 V2 V100R002C00SPC108 and earlier versions, Tecal CH121 V100R001C00SPC180 and earlier versions, Tecal CH140 V100R001C00SPC110 and earlier versions, Tecal CH220 V100R001C00SPC180 and earlier versions, Tecal CH221 V100R001C00SPC180 and earlier versions, Tecal CH222 V100R002C00SPC180 and earlier versions, Tecal CH240 V100R001C00SPC180 and earlier versions, Tecal CH242 V100R001C00SPC180 and earlier versions, Tecal CH242 V3 V100R001C00SPC110 and earlier versions could allow attackers to figure out the RMCP+ session IDs of users and access the system with forged identities.

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 confidence

The vulnerability allows remote attackers to discover or predict RMCP+ (Remote Management Control Protocol Plus) session IDs used for authentication in the IPMI (Intelligent Platform Management Interface) management interface on Huawei Tecal servers. By extrapolating valid session identifiers, attackers can forge identities and hijack legitimate administrative sessions, gaining unauthorized access to server management functions.

MitigationApply vendor-supplied firmware updates for all affected models to patched versions beyond V100R002C00SPC107/V100R002C00SPC115/etc as applicable. If patches are unavailable, restrict network access to management ports (typically UDP 623 for RMCP+) to trusted management networks only, and consider disabling remote IPMI out-of-band management if not required.

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
Tecal Rh1288 V2 FirmwareOperating system
Affected:<= v100r002c00spc107
Tecal Rh2265 V2 FirmwareOperating system
Affected:= v100r002c00
Tecal Rh2285 V2 FirmwareOperating system
Affected:<= v100r002c00spc115
Tecal Rh2285h V2 FirmwareOperating system
Affected:<= v100r002c00spc111
Tecal Rh2268 V2 FirmwareOperating system
Affected:= v100r002c00
Tecal Rh2288 V2 FirmwareOperating system
Affected:<= v100r002c00spc117
Tecal Rh2288h V2 FirmwareOperating system
Affected:<= v100r002c00spc115
Tecal Rh2485 V2 FirmwareOperating system
Affected:<= v100r002c00spc502

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.0/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 server model
    Check if the server is a Huawei Tecal model from the following list: Rh1288 V2, Rh2265 V2, Rh2285 V2, Rh2285h V2, Rh2268 V2, Rh2288 V2, Rh2288h V2, or Rh2485 V2. Use 'dmidecode -s system-product-name' or check physical labels.
    Affected if The server is NOT one of these eight models, then it is not affected by this CVE.
  2. Check firmware version
    Retrieve the current firmware version via IPMI web interface, iLO/IMM equivalent, or by running 'ipmitool -I lanplus -H <bmc_ip> -U <user> raw' commands. Compare against affected versions: Rh1288 V2 <= v100r002c00spc107, Rh2265 V2 = v100r002c00, Rh2285 V2 <= v100r002c00spc115, Rh2285h V2 <= v100r002c00spc111, Rh2268 V2 = v100r002c00, Rh2288 V2 <= v100r002c00spc117, Rh2288h V2 <= v100r002c00spc115, Rh2485 V2 <= v100r002c00spc502.
    Affected if The firmware version matches or is below the specified version for your model, indicating potential vulnerability.
  3. Verify IPMI/RMCP+ is enabled
    Check if UDP port 623 (RMCP+) is open and listening on the BMC (Baseboard Management Controller). Use 'nmap -sU -p 623 <bmc_ip>' or 'netstat -anu | grep 623' on the management network interface.
    Affected if Port 623 is open and responding to RMCP+ queries, enabling the attack vector.
  4. Confirm remote access configuration
    Check IPMI authentication settings via BMC web interface or 'ipmitool -I lanplus -H <bmc_ip> -U <user> lan print' to see if remote IPMI access is permitted over the network.
    Affected if Remote IPMI access is enabled and accessible from untrusted networks, making exploitation possible.

If the server is a listed Huawei Tecal model with firmware at or below the specified threshold AND IPMI/RMCP+ is exposed over the network, the environment is vulnerable to session ID prediction attacks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply vendor-supplied firmware updates for all affected models to patched versions beyond V100R002C00SPC107/V100R002C00SPC115/etc as applicable. If patches are unavailable, restrict network access to management ports (typically UDP 623 for RMCP+) to trusted management networks only, and consider disabling remote IPMI out-of-band management if not required.

Fix this in Tecal Rh1288 V2 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 help mitigating

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-2014-9692 — 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-2014-9692 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