# CVE-2018-7941: Auth bypass in iBMC

> Remote attackers can bypass authentication to upload certificates, leading to privilege escalation on Huawei iBMC systems.

- **Severity:** High 8.8 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 May 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3jmp-4qpg-7fv3

## What is CVE-2018-7941?

CVE-2018-7941 is a high-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. iBMC, published on 10 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Huawei 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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2018-7941?

It affects 20 products.


Products: Huawei 1288h V5 Firmware, Huawei 2288h V5 Firmware, Huawei 2488 V5 Firmware, Huawei Ch121 V3 Firmware, Huawei Ch121 V5 Firmware, Huawei Ch121l V3 Firmware, Huawei Ch121l V5 Firmware, Huawei Ch140 V3 Firmware, Huawei Ch140l V3 Firmware, Huawei Ch220 V3 Firmware, Huawei Ch222 V3 Firmware, Huawei Ch242 V3 Firmware, Huawei Ch242 V5 Firmware, Huawei Rh1288 V3 Firmware, Huawei Rh2288 V3 Firmware, Huawei Rh2288h V3 Firmware, Huawei Xh310 V3 Firmware, Huawei Xh321 V3 Firmware, Huawei Xh321 V5 Firmware, Huawei Xh620 V3 Firmware.

## How do I fix CVE-2018-7941?

No fix has been published for CVE-2018-7941 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-7941 being exploited?

There is no known exploitation of CVE-2018-7941 in the wild and no public exploit code.

## Other vulnerabilities in Huawei Technologies Co., Ltd. iBMC

- [CVE-2018-7943](https://insights.sbomify.com/CVE-2018-7943/): Auth bypass in 1288H V5; 2288H V5; 2488 V5 ; CH121 V3; CH121L V3; CH121L V5 ; CH121 V5 ; CH140 V3; CH140L V3; CH220 V3; CH222 V3; CH242 V3; CH242 V5 ; RH1288 V3; RH2288 V3; RH2288H V3; XH310 V3; XH321 V3; XH321 V5; XH620 V3 (high 8.8)
- [CVE-2018-7949](https://insights.sbomify.com/CVE-2018-7949/): Privilege escalation in 1288H V5; 2288H V5; 2488 V5 ; CH121 V3; CH121L V3; CH121L V5 ; CH121 V5 ; CH140 V3; CH140L V3; CH220 V3; CH222 V3; CH242 V3; CH242 V5 ; RH1288 V3; RH2288 V3; RH2288H V3; XH310 V3; XH321 V3; XH321 V5; XH620 V3 (high 8.8)
- [CVE-2018-7950](https://insights.sbomify.com/CVE-2018-7950/): Code injection in 1288H V5; 2288H V5; 2488 V5 ; CH121 V3; CH121L V3; CH121L V5 ; CH121 V5 ; CH140 V3; CH140L V3; CH220 V3; CH222 V3; CH242 V3; CH242 V5 ; RH1288 V3; RH2288 V3; RH2288H V3; XH310 V3; XH321 V3; XH321 V5; XH620 V3 (high 8.8)
- [CVE-2018-7951](https://insights.sbomify.com/CVE-2018-7951/): Code injection in 1288H V5; 2288H V5; 2488 V5 ; CH121 V3; CH121L V3; CH121L V5 ; CH121 V5 ; CH140 V3; CH140L V3; CH220 V3; CH222 V3; CH242 V3; CH242 V5 ; RH1288 V3; RH2288 V3; RH2288H V3; XH310 V3; XH321 V3; XH321 V5; XH620 V3 (high 8.8)
- [CVE-2018-7902](https://insights.sbomify.com/CVE-2018-7902/): Code injection in 1288H V5; 2288H V5 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7941 and fix it if it is affected.

What it is: CVE-2018-7941 is a high-severity authentication bypass vulnerability in Huawei Technologies Co., Ltd. iBMC, published on 10 May 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7941 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. iBMC. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-7941/ (Markdown: https://insights.sbomify.com/CVE-2018-7941/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7941
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7941
- OSV: https://osv.dev/vulnerability/CVE-2018-7941

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-7941/
Summaries are generated and may contain mistakes; the official description above is the record.