1288h V5 FirmwareOperating system · Huawei

CVE-2018-7950

HIGH · 8.8 CVSS v3.0 Published 2018-06-01
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 iBMC (Intelligent Baseboard Management Controller) of some Huawei servers have a JSON injection vulnerability due to insufficient input validation. An authenticated, remote attacker can launch a JSON injection to modify the password of administrator. Successful exploit may allow attackers to obtain the management privilege of the system.

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 iBMC (Intelligent Baseboard Management Controller) on Huawei servers contains a JSON injection vulnerability due to insufficient input validation. An authenticated remote attacker can inject malicious JSON payload to modify the administrator password and gain full management privileges of the affected system.

MitigationApply the vendor-supplied firmware/patch for iBMC from Huawei's security advisory. If immediate patching is not feasible, restrict network access to the iBMC management interface to trusted IP addresses and enforce strong authentication mechanisms.

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
1288h V5 FirmwareOperating system
Affected:= 100r005c00
2288h V5 FirmwareOperating system
Affected:= 100r005c00
2488 V5 FirmwareOperating system
Affected:= 100r005c00
Ch121 V3 FirmwareOperating system
Affected:= 100r001c00
Ch121l V3 FirmwareOperating system
Affected:= 100r001c00
Ch121l V5 FirmwareOperating system
Affected:= 100r001c00
Ch121 V5 FirmwareOperating system
Affected:= 100r001c00
Ch140 V3 FirmwareOperating system
Affected:= 100r001c00

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 if the server is a Huawei model with iBMC
    Check the server hardware model (1288h V5, 2288h V5, 2488 V5, Ch121 V3, Ch121l V3, Ch121l V5, Ch121 V5, or Ch140 V3) and confirm iBMC (Intelligent Baseboard Management Controller) is present
    Affected if The server is one of the listed Huawei models and has iBMC firmware installed
  2. Check the iBMC firmware version
    Access the iBMC web interface or use the command line (e.g., 'ipmcget -t version' or similar iBMC CLI command) to retrieve the firmware version
    Affected if The firmware version matches exactly 100r005c00 for V5 models or 100r001c00 for V3/V5 Ch models (these are the affected versions listed)
  3. Verify iBMC remote management interface is accessible
    Check if the iBMC web interface (HTTPS/HTTP port) or IPMI over network is reachable from network segments outside the server itself
    Affected if iBMC is network-accessible and an attacker could potentially authenticate to it
  4. Confirm iBMC user authentication is enabled
    Review iBMC user accounts and authentication settings to ensure user accounts exist and remote authentication (local or LDAP/RADIUS) is configured
    Affected if Remote authentication is enabled, as the vulnerability requires an authenticated attacker to inject the malicious JSON payload

You are affected if you run any of the listed Huawei server models with iBMC firmware version 100r005c00 or 100r001c00, have iBMC network-accessible, and allow remote authentication.

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 vendor-supplied firmware/patch for iBMC from Huawei's security advisory. If immediate patching is not feasible, restrict network access to the iBMC management interface to trusted IP addresses and enforce strong authentication mechanisms.

Fix this in 1288h V5 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-2018-7950 — 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-2018-7950 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