CVE-2024-23690
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceCommand injection vulnerability in the Telnet interface of end-of-life Netgear FVS336Gv2 and FVS336Gv3 firewalls allows an authenticated remote attacker to execute arbitrary OS commands as root by sending crafted 'util backup_configuration' commands.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify device modelAccess the device web interface or console and check the model number under Status or System Info sectionAffected if Device model is FVS336Gv2 or FVS336Gv3
-
Verify Telnet service statusAttempt to connect to the device on Telnet port 23 using telnet <device-ip> or scan the device for open port 23Affected if Telnet port 23 is open and accepting connections
-
Check authentication exposureDetermine if default or weak Telnet credentials are still in use, or if Telnet is accessible from untrusted networksAffected if Telnet is accessible with valid administrative credentials
-
Review configuration for util backup_configurationInspect any saved configurations or device logs for evidence of 'util backup_configuration' command usageAffected if Configuration or logs contain references to the util backup_configuration command or unexpected command execution patterns
You are affected if you are running a FVS336Gv2 or FVS336Gv3 device with Telnet port 23 exposed and accessible using valid credentials.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedSince these devices are end-of-life with no vendor patches available, disable Telnet access immediately, isolate the devices on a restricted network segment, and plan for replacement with supported hardware.
- Replace the end-of-life Netgear FVS336Gv2 and FVS336Gv3 devices with currently supported hardware that receives security updates.
- If immediate replacement is not feasible, disable the Telnet interface entirely via the device management console.
- If Telnet is absolutely required for legacy operations, restrict network access to the Telnet port (port 23) using firewall rules to allow only trusted management IPs.
- Implement network segmentation to isolate the affected devices from sensitive network segments.
- Monitor for any unexpected administrative activity or unusual outbound connections indicative of compromise.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,912.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-23690 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-23690 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data