# CVE-2020-6862: Auth bypass in F6x2W

> Unauthorized users can bypass verification code requirements to log in and access page information on ZTE F6x2W devices.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Jan 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-x239-hf9w-jv5x

## What is CVE-2020-6862?

CVE-2020-6862 is a medium-severity authentication bypass vulnerability in ZTE Corporation F6x2W, published on 17 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

V6.0.10P2T2 and V6.0.10P2T5 of F6x2W product are impacted by Information leak vulnerability. Unauthorized users could log in directly to obtain page information without entering a verification code.

Weakness: CWE-669 (Incorrect Resource Transfer Between Spheres)

## Which versions are affected by CVE-2020-6862?

It affects 1 product.


Products: Zte F6x2w Firmware.

## How do I fix CVE-2020-6862?

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

## Is CVE-2020-6862 being exploited?

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

Public exploit code:

- ZTE Router F602W - Captcha Bypass (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-6862 and fix it if it is affected.

What it is: CVE-2020-6862 is a medium-severity authentication bypass vulnerability in ZTE Corporation F6x2W, published on 17 Jan 2020. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-6862 in the wild and no public exploit code.

Affected product: ZTE Corporation F6x2W. 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-2020-6862/ (Markdown: https://insights.sbomify.com/CVE-2020-6862/index.md)
```

## Sources

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

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