dbcve.org
Rh2288 V3 FirmwareOperating system · Huawei

CVE-2015-7842

HIGH · 7.1 CVSS v3.0 Published 2017-10-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
77/100
Remediation priority · High
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
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 allow remote authenticated operators to change server information by leveraging failure to verify user permissions.

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 an authorization bypass vulnerability in Huawei FusionServer rack servers where remote authenticated operators can change server information due to the system failing to properly verify user permissions. An operator-level user can perform administrative-level actions to modify server configuration data, representing a privilege escalation issue.

MitigationUpgrade the server software to the specified version for each model (e.g., RH2288 V3 to V100R003C00SPC603 or later) to include the permission verification fix.

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
Rh2288 V3 FirmwareOperating system
Affected:<= v100r003c00
Rh2288h V3 FirmwareOperating system
Affected:<= v100r003c00
Xh628 V3 FirmwareOperating system
Affected:<= v100r003c00
Rh1288 V3 FirmwareOperating system
Affected:<= v100r003c00spc100
Rh2288a V2 FirmwareOperating system
Affected:<= v100r002c00
Rh1288a V2 FirmwareOperating system
Affected:<= v100r002c00
Rh8100 V3 FirmwareOperating system
Affected:<= v100r003c00
Ch222 V3 FirmwareOperating system
Affected:<= v100r001c00

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
None
Integrity
Low
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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 the Huawei server model
    Access the iBMC/BIOS interface or check the physical server label to determine the exact model (e.g., Rh2288 V3, Rh2288h V3, Xh628 V3, Rh1288 V3, Rh2288a V2, Rh1288a V2, Rh8100 V3, or Ch222)
    Affected if The server model matches one of the affected models listed in the CVE
  2. Retrieve the current firmware version
    Log into the iBMC (Intelligent Baseboard Management Controller) web interface or CLI and run the command to display firmware version (typically 'ipmcget -t version' or check the System Information page)
    Affected if Unable to retrieve firmware version from the iBMC interface
  3. Compare firmware version against affected ranges
    Match your firmware version to the affected threshold for your model: Rh2288 V3, Rh2288h V3, Xh628 V3, Rh8100 V3 must be <= v100r003c00; Rh1288 V3 must be <= v100r003c00spc100; Rh2288a V2 and Rh1288a V2 must be <= v100r002c00; Ch222 V3 must be <= v100r001c00
    Affected if Your installed firmware version is at or below the threshold for your specific model
  4. Verify if operator-level accounts exist
    Check the iBMC user management section to determine if any operator-level accounts are configured (operator role has more privileges than standard users but fewer than administrators)
    Affected if Operator-level accounts exist in the iBMC user database

You are affected if your server is one of the eight listed models AND your installed firmware version is at or below the specified threshold, allowing any operator-level user to perform administrative actions.

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

Upgrade the server software to the specified version for each model (e.g., RH2288 V3 to V100R003C00SPC603 or later) to include the permission verification fix.

Fix this in Rh2288 V3 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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