dbcve.org
Rv042 FirmwareOperating system · Cisco

CVE-2024-20517

MEDIUM · 6.8 CVSS v3.1 Published 2024-10-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
A vulnerability in the web-based management interface of Cisco Small Business RV042, RV042G, RV320, and RV325 Routers could allow an authenticated, Administrator-level, remote attacker to cause an unexpected reload of an affected device, resulting in a denial of service (DoS) condition. To exploit this vulnerability, an attacker would need to have valid Administrator credentials on the affected device.   This vulnerability is due to improper validation of user input that is in incoming HTTP packets. An attacker could exploit this vulnerability by sending a crafted HTTP request to the web-based management interface of the affected device. A successful exploit could allow the attacker to cause an unexpected reload of the device, resulting in a DoS condition.

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 confidence

The vulnerability exists in the web-based management interface of Cisco Small Business RV042, RV042G, RV320, and RV325 routers. Improper validation of user input in incoming HTTP packets allows an authenticated Administrator-level attacker to send a crafted HTTP request that causes an unexpected device reload, resulting in denial of service.

MitigationApply the vendor firmware update when available. In the interim, restrict access to the web-based management interface to trusted networks or IP addresses only, and enforce strong Administrator credential policies.

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
Rv042 FirmwareOperating system
Affected:= 1.0.1.17= 1.0.2.03= 1.1.0.09= 1.1.1.06= 1.1.1.19= 1.2.1.13= 1.2.1.14= 1.3.1.10= 1.3.1.12= 1.3.2.02= 1.3.12.6-tm= 1.3.12.19-tm
Rv042g FirmwareOperating system
Affected:= 1.0.1.17= 1.0.2.03= 1.1.0.09= 1.1.1.06= 1.1.1.19= 1.2.1.13= 1.2.1.14= 1.3.1.10= 1.3.1.12= 1.3.2.02= 1.3.12.6-tm= 1.3.12.19-tm
Rv320 FirmwareOperating system
Affected:= 1.0.1.17= 1.0.2.03= 1.1.0.09= 1.1.1.06= 1.1.1.19= 1.2.1.13= 1.2.1.14= 1.3.1.10= 1.3.1.12= 1.3.2.02= 1.3.12.6-tm= 1.3.12.19-tm
Rv325 FirmwareOperating system
Affected:= 1.0.1.17= 1.0.2.03= 1.1.0.09= 1.1.1.06= 1.1.1.19= 1.2.1.13= 1.2.1.14= 1.3.1.10= 1.3.1.12= 1.3.2.02= 1.3.12.6-tm= 1.3.12.19-tm

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
Changed
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router model
    Access the web-based management interface and navigate to Status > System Summary, or check the device label/console output to confirm the model is RV042, RV042G, RV320, or RV325
    Affected if The model is one of RV042, RV042G, RV320, or RV325
  2. Locate the firmware version
    In the web UI, go to Status > System Summary and locate the Firmware Version field; alternatively, check the login page footer or the router's console boot sequence
    Affected if The installed firmware version is displayed on the device
  3. Compare version to affected list
    Match the installed firmware version against the affected versions: 1.0.1.17, 1.0.2.03, 1.1.0.09, 1.1.1.06, 1.1.1.19, 1.2.1.13, 1.2.1.14, 1.3.1.10, 1.3.1.12, 1.3.2.02, 1.3.12.6-tm, or 1.3.12.19-tm
    Affected if The installed version exactly matches one of the listed versions for your model
  4. Verify web management interface is accessible
    Confirm the router's web-based management interface (HTTP/HTTPS on ports 80 or 443) is reachable from your network by attempting to access the router's IP in a browser
    Affected if The web management interface is enabled and reachable
  5. Confirm administrator access exists
    Review user accounts in the web UI under Administration > User Management to determine if any Administrator-level accounts are configured, or check for active sessions
    Affected if Administrator-level credentials are configured or active on the device (the vulnerability requires an authenticated Administrator attacker)

The device is affected if it is an RV042, RV042G, RV320, or RV325 model running any of the 12 listed firmware versions and its web-based management interface is accessible to an authenticated Administrator.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor firmware update when available. In the interim, restrict access to the web-based management interface to trusted networks or IP addresses only, and enforce strong Administrator credential policies.

Fix this in Rv042 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,540
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,464.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20517 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-20517 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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