CVE-2018-7941
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 · uneditedHuawei iBMC V200R002C60 have an authentication bypass vulnerability. A remote attacker with low privilege may craft specific messages to upload authentication certificate to the affected products. Due to improper validation of the upload authority, successful exploit may cause privilege elevation.
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 confidenceHuawei iBMC V200R002C60 contains an authentication bypass vulnerability where improper validation of upload authority allows a low-privilege remote attacker to craft specific messages to upload authentication certificates, resulting in privilege elevation.
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= 100r001c00= 100r001c00= 100r001c00= 100r001c00= 100r001c00= 100r001c00= 100r001c00= 100r003c00CVSS 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 server hardware modelAccess the BMC web interface or use IPMI commands (ipmitool chassis identify or similar) to determine the exact server model (e.g., Ch121 V3, Ch121l V3, Ch140 V3, Ch140l V3, Ch220 V3, Ch222 V3, Ch242 V3, or Rh1288 V3).Affected if The server model matches one of the affected models listed in the CVE (any Ch121/Ch121l/Ch140/Ch140l/Ch220/Ch222/Ch242 V3 or Rh1288 V3).
-
Check the iBMC firmware versionLog into the BMC management interface (web UI or CLI via IPMI/redfish) and navigate to the firmware information or about section to retrieve the iBMC version. The version format appears as V200R002C60 or similar.Affected if The iBMC firmware version is V200R002C60 exactly.
-
Verify the firmware revision numberIn the BMC firmware details, check the firmware revision or build number. For Ch-series models, look for 100r001c00; for Rh1288 V3, look for 100r003c00.Affected if The firmware revision matches 100r001c00 (Ch-series) or 100r003c00 (Rh1288 V3).
-
Inspect certificate upload capability for low-privilege usersReview the BMC user privileges and access control settings. Determine if users with low privilege levels (e.g., read-only or operator accounts) have the ability to access the certificate upload or authentication configuration functions.Affected if Low-privilege BMC users can access or execute certificate upload operations without proper authorization checks.
-
Audit existing authentication certificatesExamine the BMC certificate store or authentication configuration for any unexpected or unauthorized client or server certificates that were not intentionally deployed by administrators.Affected if Unexpected or unrecognized certificates are present in the BMC authentication configuration.
A server is affected if it is a Ch121/Ch121l/Ch140/Ch140l/Ch220/Ch222/Ch242 V3 or Rh1288 V3 model running iBMC V200R002C60 firmware with revision 100r001c00 or 100r003c00 respectively.
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 the vendor-provided patch for V200R002C60. Review and regenerate authentication certificates after patching to ensure no unauthorized certificates were uploaded during potential exploitation.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7941 — 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-7941 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