# CVE-2018-7900: Information disclosure in some HG products

> An attacker can exploit an information leak vulnerability in Huawei HG devices to obtain sensitive device information.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **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:** 2 Jan 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4rq5-mqfw-3wq4

## What is CVE-2018-7900?

CVE-2018-7900 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. some HG products, published on 2 Jan 2019. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

There is an information leak vulnerability in some Huawei HG products. An attacker may obtain information about the HG device by exploiting this vulnerability.

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

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

It affects 6 products.


Products: Huawei Hg8010h Firmware, Huawei Hg8040h Firmware, Huawei Hg8045q Firmware, Huawei Hg8110h Firmware, Huawei Hg8240h Firmware, Huawei Hg8242h Firmware.

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

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

## Is CVE-2018-7900 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7900 is a medium-severity vulnerability in Huawei Technologies Co., Ltd. some HG products, published on 2 Jan 2019. 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-7900 in the wild and no public exploit code.

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

## Sources

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

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