dbcve.org
Fusionserver Ch121 V3Application · Huawei

CVE-2015-7843

HIGH · 8.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 →
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 management interface 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 does not limit the number of query attempts, which allows remote authenticated users to obtain credentials of higher-level users via a brute force attack.

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

This is a brute force vulnerability in Huawei FusionServer rack server management interfaces (iBMC). The web-based management interface lacks rate limiting or account lockout mechanisms, allowing authenticated users to repeatedly attempt password guessing until they successfully compromise higher-privilege user accounts.

MitigationUpdate firmware to the specified versions (e.g., RH2288 V3 to V100R003C00SPC603) to patch the vulnerability. Additionally, restrict network access to the management interface using firewall rules or VLAN isolation to reduce attack surface.

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
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 iBMC web interface exposure
    Determine if the iBMC web management interface (typically on ports 80/443 or 4430/4431) is accessible from network segments outside the management VLAN. Use a port scan or firewall rule review to confirm external accessibility.
    Affected if The iBMC web interface is reachable from untrusted networks or the internet.
  2. Check iBMC firmware version
    Log into the iBMC web interface and navigate to the firmware/version information page, or use the ipmitool command 'ipmitool -I lanplus -H <iBMC_IP> -U <user> mc info' to retrieve the iBMC firmware version. Compare against the affected version list.
    Affected if The installed version matches any of: CH121 V3 = v100r001c00, CH220 V3 = v100r001c00, CH222 V3 = v100r001c00, RH1288 V3 = v100r003c00spc100, RH1288a V2 = v100r002c00, RH2288 V3 = v100r003c00, RH2288a V2 = v100r002c00, RH2288h V3 = v100r003c00.
  3. Verify account lockout configuration
    Access the iBMC web interface security settings or user management section. Look for account lockout or password retry limit policies. Check if there is a configurable option for failed login attempts before account lockout, and whether it is enabled.
    Affected if No account lockout policy is configured, or the lockout threshold is set to unlimited/unrestricted, allowing unlimited password attempts.

A user is affected if the iBMC web interface is network-accessible and the firmware version matches an affected version listed in the CVE without an account lockout or rate-limiting mechanism configured.

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

Update firmware to the specified versions (e.g., RH2288 V3 to V100R003C00SPC603) to patch the vulnerability. Additionally, restrict network access to the management interface using firewall rules or VLAN isolation to reduce attack surface.

Fix this in Fusionserver Ch121 V3 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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