Tecal E9000 Chassis FirmwareOperating system · Huawei

CVE-2014-9696

HIGH · 8.8 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 →
94/100
Remediation priority · Urgent
Remotely reachable 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
The Hyper Module Management (HMM) software of Huawei Tecal E9000 Chassis V100R001C00SPC160 and earlier versions allows the operator to modify the user configuration of iMana through privilege escalation.

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

The Hyper Module Management (HMM) software in Huawei Tecal E9000 Chassis contains a privilege escalation vulnerability (CVSS 8.8) that allows an operator to modify user configuration of the iMana management interface without proper authorization. This enables unauthorized modification of user settings and permissions within the chassis management system.

MitigationApply the Huawei firmware update for HMM to a version later than V100R001C00SPC160, and restrict network access to the iMana management interface to authorized personnel only.

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 E9000 Chassis FirmwareOperating system
Affected:<= v100r001c00spc160

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Huawei Tecal E9000 Chassis in environment
    Locate the hardware asset inventory or physically inspect the chassis for Huawei Tecal E9000 model labeling. Confirm the device is an E9000 Chassis management blade.
    Affected if The environment contains a Huawei Tecal E9000 Chassis system
  2. Determine HMM firmware version
    Access the iMana web management interface (typically via https://[chassis-ip]/imanaworker), navigate to the HMM firmware information section, or use the command line: `ipmcget -t version -d hmmversion` via IPMI. Record the displayed HMM firmware version.
    Affected if HMM firmware version is v100r001c00spc160 or earlier (any version <= v100r001c00spc160)
  3. Verify iMana management interface is network accessible
    Check if TCP ports 443, 80, or 623 (IPMI) for the iMana interface are open and reachable from network segments. Use `nmap -p 80,443,623 [chassis-ip]` or similar network scanning tool.
    Affected if The iMana management interface is exposed on the network and accessible to operators who should not have configuration privileges
  4. Inspect user configuration access controls
    Log into the iMana interface with an operator-level account (not administrator). Attempt to navigate to User Management or Configuration settings. Check if the account can modify user settings, add users, or change permissions without elevated admin credentials.
    Affected if Non-administrator accounts can modify user configurations, roles, or permissions within iMana

The environment is affected if a Huawei Tecal E9000 Chassis with HMM firmware version v100r001c00spc160 or earlier has its iMana management interface accessible, allowing unauthorized users to modify user configurations.

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 the Huawei firmware update for HMM to a version later than V100R001C00SPC160, and restrict network access to the iMana management interface to authorized personnel only.

Fix this in Tecal E9000 Chassis Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-9696 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-9696 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