dbcve.org
Fusionserver Ch121 V3Application · Huawei

CVE-2015-7841

CRITICAL · 9.8 CVSS v3.0 Published 2017-10-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The login page of the server on Huawei FusionServer rack servers RH2288 V3 with software before V100R003C00SPC603, RH2288H V3 with software before V100R003C00SPC503, XH628 V3 with software before V100R003C00SPC602, RH1288 V3 with software before V100R003C00SPC602, RH2288A V2 with software before V100R002C00SPC701, RH1288A V2 with software before V100R002C00SPC502, RH8100 V3 with software before V100R003C00SPC110, CH222 V3 with software before V100R001C00SPC161, CH220 V3 with software before V100R001C00SPC161, and CH121 V3 with software before V100R001C00SPC161 allows remote attackers to bypass access restrictions and enter commands via unspecified parameters, as demonstrated by a "user creation command."

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

Authentication bypass vulnerability in Huawei FusionServer rack server BMC (Baseboard Management Controller) login pages. Remote unauthenticated attackers can bypass access controls and execute arbitrary commands (demonstrated with user creation) by manipulating unspecified parameters in the login functionality. This affects multiple RH2288, RH1288, RH8100, and CH series models across V2 and V3 generations.

MitigationUpdate affected server BMC firmware to the specified version thresholds: RH2288 V3 to V100R003C00SPC603, RH2288H V3 to V100R003C00SPC503, XH628 V3 to V100R003C00SPC602, RH1288 V3 to V100R003C00SPC602, RH2288A V2 to V100R002C00SPC701, RH1288A V2 to V100R002C00SPC502, RH8100 V3 to V100R003C00SPC110, CH222/CH220/CH121 V3 to V100R001C00SPC161 or later.

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
Fusionserver Ch121 V3Application
Affected:= v100r001c00
Fusionserver Ch220 V3Application
Affected:= v100r001c00
Fusionserver Ch222 V3Application
Affected:= v100r001c00
Fusionserver Rh1288 V3Application
Affected:= v100r003c00spc100
Fusionserver Rh1288a V2Application
Affected:= v100r002c00
Fusionserver Rh2288 V3Application
Affected:= v100r003c00
Fusionserver Rh2288a V2Application
Affected:= v100r002c00
Fusionserver Rh2288h V3Application
Affected:= v100r003c00

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
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 checks

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

  1. Identify BMC model and firmware version
    Access the BMC web interface or use IPMI command 'ipmitool -I lanplus -H <BMC_IP> -U admin -P admin raw hex' to retrieve version information. Common IPMI commands: 'ipmitool -I lanplus -H <BMC_IP> -U admin -P admin mc info' or check the 'Maintenance > Firmware Update' page in the BMC web interface.
    Affected if The model matches any of: CH121 V3, CH220 V3, CH222 V3, RH1288 V3, RH1288A V2, RH2288 V3, RH2288A V2, RH2288H V3, and the firmware version exactly matches the affected versions listed in the CVE (v100r001c00, v100r003c00spc100, v100r002c00, v100r003c00).
  2. Verify BMC is network accessible
    Confirm the BMC IP address is reachable from untrusted networks by attempting ping or TCP connection to ports 80/443 on the BMC IP. Check if the BMC management interface is exposed to the internet or untrusted VLANs.
    Affected if The BMC management interface (typically ports 80, 443, or 623 UDP for IPMI) is reachable from an untrusted network, making remote exploitation possible.
  3. Confirm BMC login interface is exposed
    Attempt HTTP/HTTPS access to the BMC login page (http://<BMC_IP> or https://<BMC_IP>). Verify whether the login form is accessible without authentication.
    Affected if The BMC login page is accessible remotely without prior authentication, which is the attack vector for this CVE.
  4. Compare installed firmware to patched versions
    Document the exact firmware version installed. Compare against the known patched versions: RH2288 V3 should be >= V100R003C00SPC603, RH2288H V3 >= V100R003C00SPC503, RH1288 V3 >= V100R003C00SPC602, RH2288A V2 >= V100R002C00SPC701, RH1288A V2 >= V100R002C00SPC502, CH222/CH220/CH121 V3 >= V100R001C00SPC161.
    Affected if The installed firmware version is EQUAL TO the affected version and has not been updated to the minimum patched version for that specific model.

Your environment is affected if you have a Huawei FusionServer BMC (RH1288, RH2288, RH2288H, RH2288A, RH8100, or CH series) running firmware versions exactly matching those listed in the CVE, and the BMC is network-accessible to untrusted users.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update affected server BMC firmware to the specified version thresholds: RH2288 V3 to V100R003C00SPC603, RH2288H V3 to V100R003C00SPC503, XH628 V3 to V100R003C00SPC602, RH1288 V3 to V100R003C00SPC602, RH2288A V2 to V100R002C00SPC701, RH1288A V2 to V100R002C00SPC502, RH8100 V3 to V100R003C00SPC110, CH222/CH220/CH121 V3 to V100R001C00SPC161 or later.

Recommended fix High confidence

Upgrade to vendor-specified patch level: RH2288 V3 to V100R003C00SPC603+, RH2288H V3 to V100R003C00SPC503+, RH1288 V3 to V100R003C00SPC602+, RH2288A V2 to V100R002C00SPC701+, RH1288A V2 to V100R002C00SPC502+, CH121/220/222 V3 to V100R001C00SPC161+

  1. 1. Identify the exact model and current software version of the affected FusionServer by accessing the iBMC or iMana web interface or using CLI.
  2. 2. Download the appropriate firmware/patch file from Huawei's official support portal (www1.huawei.com) matching your specific model and the minimum fixed version: RH2288 V3 requires V100R003C00SPC603 or later; RH2288H V3 requires V100R003C00SPC503 or later; RH1288 V3 requires V100R003C00SPC602 or later; RH2288A V2 requires V100R002C00SPC701 or later; RH1288A V2 requires V100R002C00SPC502 or later
  3. 3. Create a full backup of the current server configuration and, if possible, take an image backup of the management firmware.
  4. 4. Upload the firmware upgrade file through the iBMC web interface (Firmware Update section) or via CLI using the 'ipmcset -t upgrade' command.
  5. 5. Initiate the firmware upgrade and monitor the process to completion; do not power off the server during the upgrade.
  6. 6. After upgrade completes, verify the new software version matches or exceeds the required fixed version.
  7. 7. Verify the vulnerability is remediated by confirming the login page no longer accepts command injection in unspecified parameters.
Caveat Firmware upgrades on BMC/iBMC systems may cause temporary management interface unavailability; ensure out-of-band management access is available and plan for brief downtime

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Fusionserver Ch121 V3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-7841 — 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-2015-7841 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