CVE-2018-7949
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 · uneditedThe iBMC (Intelligent Baseboard Management Controller) of some Huawei servers have a privilege escalation vulnerability. A remote attacker may send some specially crafted login messages to the affected products. Due to improper authentication design, successful exploit enables low privileged users to get or modify passwords of highly privileged users.
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 · moderate confidenceThe iBMC (Intelligent Baseboard Management Controller) on affected Huawei servers contains an improper authentication design flaw. A remote attacker can send specially crafted login messages to exploit this vulnerability, allowing a low-privileged user to obtain or modify passwords of highly privileged users. This constitutes a privilege escalation from standard users to administrative accounts.
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= 100r005c00= 100r005c00= 100r005c00= 100r001c00= 100r001c00= 100r001c00= 100r001c00= 100r001c00CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Huawei server or chassis modelAccess the iBMC web interface, CLI via SSH, or use IPMI commands to retrieve the product name and model number. Common commands: `ipmitool -I lanplus -H <iBMC_IP> -U <user> -P <pass> fru print` or check the iBMC dashboard for the server model.Affected if The model is one of: Huawei 1288h V5, 2288h V5, 2488 V5, Ch121 V3, Ch121l V3, Ch121l V5, Ch121 V5, or Ch140 V3.
-
Retrieve the iBMC firmware versionCheck the iBMC firmware version through the iBMC web interface under 'System Information' or via CLI command `ipmitool -I lanplus -H <iBMC_IP> -U <user> -P <pass> mc info` or `show version` when logged into iBMC CLI.Affected if The iBMC firmware version is exactly 100r005c00 for V5 servers (1288h V5, 2288h V5, 2488 V5) or exactly 100r001c00 for V3/V5 chassis (Ch121 V3, Ch121l V3, Ch121l V5, Ch121 V5, Ch140 V3).
-
Verify iBMC network accessibilityConfirm that the iBMC management interface is reachable on the network. Use ping and port checks (typically ports 443, 80, 623 for IPMI) against the iBMC IP address.Affected if iBMC is network-accessible from untrusted networks. The vulnerability is exploitable remotely when iBMC is exposed.
-
Review configured iBMC user accountsList all iBMC users using IPMI command `ipmitool -I lanplus -H <iBMC_IP> -U <user> -P <pass> user list` or via the iBMC web interface user management panel.Affected if Multiple user accounts exist with varying privilege levels, including both standard users and administrative accounts. The flaw allows low-privileged users to modify admin passwords.
You are affected if your Huawei server or chassis matches one of the listed models AND the iBMC firmware version is exactly 100r005c00 (for V5 servers) or 100r001c00 (for V3/V5 chassis), and iBMC is network-accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataApply Huawei firmware updates for iBMC when available, and restrict network access to iBMC management interfaces to reduce attack surface.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7949 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2018-7949 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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