# CVE-2024-23690: EOL Netgear FVS336Gv2 and FVS336Gv3 Telnet Configuration Backup Command Injection

> Authenticated attackers can execute arbitrary OS commands as root on EOL Netgear FVS336Gv2/v3 devices via Telnet.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2025
- **Updated:** 29 Oct 2026
- **Also known as:** GHSA-693p-9gm7-mm9r

## What is CVE-2024-23690?

CVE-2024-23690 is a high-severity command injection vulnerability in Netgear FVS336Gv2, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The end-of-life Netgear FVS336Gv2 and FVS336Gv3 are affected by a command injection vulnerability in the Telnet interface. An authenticated and remote attacker can execute arbitrary OS commands as root over Telnet by sending crafted "util backup_configuration" commands.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

## Which versions are affected by CVE-2024-23690?


## How do I fix CVE-2024-23690?

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

## Is CVE-2024-23690 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-23690 and fix it if it is affected.

What it is: CVE-2024-23690 is a high-severity command injection vulnerability in Netgear FVS336Gv2, published on 4 Feb 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-23690 in the wild and no public exploit code.

Affected product: Netgear FVS336Gv2. 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-2024-23690/ (Markdown: https://insights.sbomify.com/CVE-2024-23690/index.md)
```

## Sources

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

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