CVE-2024-20470
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 · uneditedA vulnerability in the web-based management interface of Cisco Small Business RV340, RV340W, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an authenticated, remote attacker to execute arbitrary code on an affected device. In order to exploit this vulnerability, the attacker must have valid admin credentials. This vulnerability exists because the web-based management interface does not sufficiently validate user-supplied input. An attacker could exploit this vulnerability by sending crafted HTTP input to an affected device. A successful exploit could allow the attacker to execute arbitrary code as the root user on the underlying operating system.
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 confidenceThis is an authenticated command injection vulnerability in the web-based management interface of Cisco Small Business RV340/RV345 series routers. An attacker with valid admin credentials can send specially crafted HTTP requests containing malicious input that is not properly validated, allowing arbitrary code execution with root privileges on the underlying Linux-based router OS.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 1.0.00.29= 1.0.00.33= 1.0.01.16= 1.0.01.17= 1.0.01.18= 1.0.01.20= 1.0.02.16= 1.0.03.15= 1.0.03.16= 1.0.03.17= 1.0.03.18= 1.0.03.19= 1.0.00.29= 1.0.00.33= 1.0.01.16= 1.0.01.17= 1.0.01.18= 1.0.01.20= 1.0.02.16= 1.0.03.15= 1.0.03.16= 1.0.03.17= 1.0.03.18= 1.0.03.19= 1.0.00.29= 1.0.00.33= 1.0.01.16= 1.0.01.17= 1.0.01.18= 1.0.01.20= 1.0.02.16= 1.0.03.15= 1.0.03.16= 1.0.03.17= 1.0.03.18= 1.0.03.19= 1.0.00.29= 1.0.00.33= 1.0.01.16= 1.0.01.17= 1.0.01.18= 1.0.01.20= 1.0.02.16= 1.0.03.15= 1.0.03.16= 1.0.03.17= 1.0.03.18= 1.0.03.19CVSS 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 router modelAccess the router web management interface and check the device status page, or look at the physical device label. The affected models are RV340, RV340w, RV345, and RV345p.Affected if The router is any of these four models (RV340, RV340w, RV345, or RV345p).
-
Check firmware versionLog into the web-based management interface and navigate to Administration > Firmware Upgrade or Status/Dashboard page to view the current firmware version. Compare against the affected versions: 1.0.00.29, 1.0.00.33, 1.0.01.16, 1.0.01.17, 1.0.01.18, 1.0.01.20, 1.0.02.16, 1.0.03.15, 1.0.03.16, 1.0.03.17, 1.0.03.18, 1.0.03.19.Affected if The installed firmware version exactly matches one of these versions.
-
Confirm web management is enabledNavigate to Administration > Management in the web interface and verify that HTTP or HTTPS management access is enabled. The vulnerability exists in the web-based management interface.Affected if Web-based management (HTTP/HTTPS) is enabled and accessible.
-
Verify admin account existsCheck that at least one admin user account is configured in the router under Administration > User Manager. The attacker needs valid admin credentials to exploit this vulnerability.Affected if An admin account is configured on the router.
You are affected if you have a Cisco RV340, RV340w, RV345, or RV345p router running any of the firmware versions 1.0.00.29 through 1.0.03.19, with the web management interface enabled and an admin account configured.
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.
From vendor dataApply the vendor-provided firmware patch from Cisco. If no patch is available, restrict web management interface access to trusted networks only and enforce strong admin credential policies to reduce attack surface.
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20470 — 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-20470 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