# CVE-2023-2645: USR USR-G806 Web Management Page hard-coded password

> Attackers can remotely access the USR-G806 web management interface using hard-coded root credentials, leading to full device compromise.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 May 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-mrcf-jm53-mwx9

## What is CVE-2023-2645?

CVE-2023-2645 is a critical vulnerability in USR-G806, published on 11 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability, which was classified as critical, was found in USR USR-G806 1.0.41. Affected is an unknown function of the component Web Management Page. The manipulation of the argument username/password with the input root leads to use of hard-coded password. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. It is recommended to change the configuration settings. VDB-228774 is the identifier assigned to this vulnerability. NOTE: The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-259 (Use of Hard-coded Password)

## Which versions are affected by CVE-2023-2645?

It affects 1 product.


Products: Usr Usr-G806 Firmware.

## How do I fix CVE-2023-2645?

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

## Is CVE-2023-2645 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-2645 and fix it if it is affected.

What it is: CVE-2023-2645 is a critical vulnerability in USR-G806, published on 11 May 2023. 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-2023-2645 in the wild and no public exploit code.

Affected product: USR-G806. 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-2023-2645/ (Markdown: https://insights.sbomify.com/CVE-2023-2645/index.md)
```

## Sources

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

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