# CVE-2018-7366: Auth bypass in ZXV10 B860AV2.1 ChinaMobile

> An authentication bypass in ZTE set-top boxes allows unauthorized users to perform operations without credentials.

- **Severity:** Medium 4.3 (`CVSS:3.0/AV:P/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L`)
- **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:** 28 Dec 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-222p-485j-75xg

## What is CVE-2018-7366?

CVE-2018-7366 is a medium-severity authentication bypass vulnerability in ZTE ZXV10 B860AV2.1_ChinaMobile, published on 28 Dec 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

ZTE ZXV10 B860AV2.1 product ChinaMobile branch with the ICNT versions up to V1.3.3, the BESTV versions up to V1.2.2, the WASU versions up to V1.1.7 and the MGTV versions up to V1.4.6 have an authentication bypass vulnerability, which may allows an unauthorized user to perform unauthorized operations.

Weakness: CWE-863 (Incorrect Authorization)

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

It affects 1 product.


Products: Zte Zxv10 B860av2.1 Chinamobile Firmware.

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

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

## Is CVE-2018-7366 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-7366 is a medium-severity authentication bypass vulnerability in ZTE ZXV10 B860AV2.1_ChinaMobile, published on 28 Dec 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-7366 in the wild and no public exploit code.

Affected product: ZTE ZXV10 B860AV2.1_ChinaMobile. 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-7366/ (Markdown: https://insights.sbomify.com/CVE-2018-7366/index.md)
```

## Sources

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

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