# CVE-2022-28370: Code injection in n/a

> Attackers can install malicious firmware on Verizon 5G Home Outdoor Units due to missing cryptographic validation of update images.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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-j9q2-467q-5fww

## What is CVE-2022-28370?

CVE-2022-28370 is a high-severity code injection 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 OutDoorUnit (ODU) 3.33.101.0 devices, the RPC endpoint crtc_fw_upgrade provides a means of provisioning a firmware update for the device. /lib/functions/wnc_jsonsh/wnc_crtc_fw.sh has no cryptographic validation of the image, thus allowing an attacker to modify the installed firmware.

Weakness: CWE-345 (Insufficient Verification of Data Authenticity)

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

It affects 1 product.


Products: Verizon Lvskihp Outdoorunit Firmware.

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

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

## Is CVE-2022-28370 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-28375](https://insights.sbomify.com/CVE-2022-28375/): Command injection in n/a (critical 9.8)
- [CVE-2022-28374](https://insights.sbomify.com/CVE-2022-28374/): Command injection in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-28370 is a high-severity code injection 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-28370 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-28370/ (Markdown: https://insights.sbomify.com/CVE-2022-28370/index.md)
```

## Sources

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

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