# CVE-2022-28376: Hardcoded credentials in n/a

> Attackers can bypass authentication on Verizon 5G Home routers by deriving the admin password from the device's serial number and model string.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/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:** 3 Apr 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-g94p-m365-483p

## What is CVE-2022-28376?

CVE-2022-28376 is a high-severity vulnerability in n/a, published on 3 Apr 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Verizon 5G Home LVSKIHP outside devices through 2022-02-15 allow anyone (knowing the device's serial number) to access a CPE admin website, e.g., at the 10.0.0.1 IP address. The password (for the verizon username) is calculated by concatenating the serial number and the model (i.e., the LVSKIHP string), running the sha256sum program, and extracting the first seven characters concatenated with the last seven characters of that SHA-256 value.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-28376?

It affects 1 product.


Products: Verizon Lvskihp Firmware.

## How do I fix CVE-2022-28376?

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

## Is CVE-2022-28376 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-28376 and fix it if it is affected.

What it is: CVE-2022-28376 is a high-severity vulnerability in n/a, published on 3 Apr 2022. 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-2022-28376 in the wild and no public exploit code.

Affected product: n/a. 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-2022-28376/ (Markdown: https://insights.sbomify.com/CVE-2022-28376/index.md)
```

## Sources

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

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