# CVE-2018-7901: Security feature bypass in ALP-AL00B, BLA-AL00B

> Attackers can remotely control the keyboard by bypassing RCS authentication if they obtain the key and trick users into installing a malicious app.

- **Severity:** Medium 4.4 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 30 Apr 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3mh5-q9p2-6cqr

## What is CVE-2018-7901?

CVE-2018-7901 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. ALP-AL00B, BLA-AL00B, published on 30 Apr 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

RCS module in Huawei ALP-AL00B smart phones with software versions earlier than 8.0.0.129, BLA-AL00B smart phones with software versions earlier than 8.0.0.129 has a remote control vulnerability. An attacker can trick a user to install a malicious application. When the application connects with RCS for the first time, it needs user to manually click to agree. In addition, the attacker needs to obtain the key that RCS uses to authenticate the application. Successful exploitation may cause the attacker to control keyboard remotely.

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

It affects 2 products.


Products: Huawei Alp-Al00b Firmware, Huawei Bla-Al00b Firmware.

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

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

## Is CVE-2018-7901 being exploited?

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

## Other vulnerabilities in Huawei Technologies Co., Ltd. ALP-AL00B, BLA-AL00B

- [CVE-2018-7910](https://insights.sbomify.com/CVE-2018-7910/): Auth bypass in ALP-AL00B, ALP-TL00B, BLA-AL00B, BLA-L09C, BLA-L29C (medium 6.8)
- [CVE-2019-5302](https://insights.sbomify.com/CVE-2019-5302/): Denial of service in ALP-AL00B (medium 5.3)
- [CVE-2019-5303](https://insights.sbomify.com/CVE-2019-5303/): Denial of service in ALP-AL00B (medium 5.3)
- [CVE-2019-5235](https://insights.sbomify.com/CVE-2019-5235/): Null dereference in Harry-AL00C, Harry-AL00C-PRELOAD, Harry-AL10B, Harry-LGRP1-CHN, Harry-TL00C, Jackman-AL00D, Jackman-L03, Jackman-L21, Jackman-L22, Jackman-L23, Johnson-AL00C, Johnson-AL00IC, Johnson-AL10C, Johnson-L21C, Johnson-L21D, Johnson-L22C, Johnson-L22D, Johnson-L23C, Johnson-L42IC, Johnson-L42IE, Johnson-L42IF, Johnson-TL00D, Johnson-TL00F, Potter-AL00C, Potter-AL10A, VOGUE-AL00A, VOGUE-AL00A-PRELOAD, VOGUE-AL10C, VOGUE-AL10C-PRELOAD, VOGUE-LGRP1-CHN, VOGUE-LGRP2-OVS, VOGUE-TL00B (medium 5.3)
- [CVE-2019-19412](https://insights.sbomify.com/CVE-2019-19412/): Security feature bypass in ALP-AL00B (medium 4.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7901 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. ALP-AL00B, BLA-AL00B, published on 30 Apr 2018. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-7901 in the wild and no public exploit code.

Affected product: Huawei Technologies Co., Ltd. ALP-AL00B, BLA-AL00B. 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-7901/ (Markdown: https://insights.sbomify.com/CVE-2018-7901/index.md)
```

## Sources

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

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