# CVE-2023-38928: Command injection in n/a

> Attackers can execute arbitrary commands on Netgear R7100LG routers via the password parameter in usb_remote_invite.cgi.

- **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:** 7 Aug 2023
- **Updated:** 11 Oct 2024
- **Also known as:** GHSA-6v9m-hjp3-4h7f

## What is CVE-2023-38928?

CVE-2023-38928 is a critical command injection vulnerability in Netgear R7100lg Firmware, published on 7 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Netgear R7100LG 1.0.0.78 was discovered to contain a command injection vulnerability via the password parameter at usb_remote_invite.cgi.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 1 product.


Products: Netgear R7100lg Firmware.

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

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

## Is CVE-2023-38928 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38928 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2023-38928 is a critical command injection vulnerability in Netgear R7100lg Firmware, published on 7 Aug 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-38928 exists.

Affected product: Netgear R7100lg Firmware. 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-38928/ (Markdown: https://insights.sbomify.com/CVE-2023-38928/index.md)
```

## Sources

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

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