# CVE-2018-7921: Information disclosure in B315s-22

> Unauthenticated adjacent attackers can obtain sensitive device information from Huawei B315s-22 routers.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 Sep 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-gmx3-m2jh-3xcg

## What is CVE-2018-7921?

CVE-2018-7921 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. B315s-22, published on 12 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Huawei B315s-22 products with software of 21.318.01.00.26 have an information leak vulnerability. Unauthenticated adjacent attackers may exploit this vulnerability to obtain device information.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

It affects 1 product.


Products: Huawei B315s-22 Firmware.

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

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

## Is CVE-2018-7921 being exploited?

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

Public exploit code:

- Huawei B315s-22 - Information Leak (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7921 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. B315s-22, published on 12 Sep 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-7921 in the wild and no public exploit code.

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

## Sources

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

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