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

> Attackers can derive static RPC credentials from the device MAC address to gain unauthorized access to Verizon 5G Home units.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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:** 14 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-6hxh-v9xw-6688

## What is CVE-2022-28377?

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

### Official description

On Verizon 5G Home LVSKIHP InDoorUnit (IDU) 3.4.66.162 and OutDoorUnit (ODU) 3.33.101.0 devices, the CRTC and ODU RPC endpoints rely on a static account username/password for access control. This password can be generated via a binary included in the firmware, after ascertaining the MAC address of the IDU's base Ethernet interface, and adding the string DEVICE_MANUFACTURER='Wistron_NeWeb_Corp.' to /etc/device_info to replicate the host environment. This occurs in /etc/init.d/wnc_factoryssidkeypwd (IDU).

Weakness: CWE-521 (Weak Password Requirements)

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

It affects 2 products.


Products: Verizon Lvskihp Indoorunit Firmware, Verizon Lvskihp Outdoorunit Firmware.

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

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

## Is CVE-2022-28377 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28369](https://insights.sbomify.com/CVE-2022-28369/): File upload in n/a (critical 9.8)
- [CVE-2022-28373](https://insights.sbomify.com/CVE-2022-28373/): Command injection in n/a (critical 9.8)
- [CVE-2022-28371](https://insights.sbomify.com/CVE-2022-28371/): Hardcoded credentials in n/a (high 7.5)
- [CVE-2022-28372](https://insights.sbomify.com/CVE-2022-28372/): File upload in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28377 is a high-severity vulnerability in n/a, published on 14 Jul 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-28377 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-28377/ (Markdown: https://insights.sbomify.com/CVE-2022-28377/index.md)
```

## Sources

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

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