CVE-2024-20393
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 elevate privileges on an affected device. This vulnerability exists because the web-based management interface discloses sensitive information. An attacker could exploit this vulnerability by sending crafted HTTP input to an affected device. A successful exploit could allow an attacker to elevate privileges from guest to admin.
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 vulnerability in Cisco Small Business RV340/RV340W/RV345/RV345P routers allows an authenticated attacker with guest-level access to escalate to admin privileges. The web-based management interface improperly discloses sensitive information that can be harvested via crafted HTTP requests, enabling the privilege escalation.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 modelCheck the physical device label or access the web management interface and look for the model number (RV340, RV340W, RV345, or RV345P) displayed on the status or system info pageAffected if The model is one of RV340, RV340W, RV345, or RV345P
-
Check firmware versionLog into the web management interface and navigate to Status > System Summary or Administration > Firmware Upgrade to view the installed firmware versionAffected if The firmware version matches one of these: 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
-
Verify web management is enabledNavigate to Administration > Management Interface or similar section in the web UI and check if HTTP/HTTPS management access is enabledAffected if Web-based management interface is accessible (enabled) on any interface (LAN or WAN)
-
Check for guest user accountsNavigate to User Management or Accounts in the web interface and review whether guest-level user accounts exist with limited privilegesAffected if Guest-level or limited-privilege user accounts are configured on the device
You are affected if you have a Cisco RV340/RV340W/RV345/RV345P router running one of the listed firmware versions with web management enabled and guest or low-privilege accounts present.
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-supplied firmware update for the affected RV series routers. If patches are unavailable, restrict web management interface access to trusted internal networks only and disable remote management where feasible.
- Consultation4.0 h
- Implementation4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-20393 — 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-20393 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