dbcve.org
Rv042 FirmwareOperating system · Cisco

CVE-2024-20523

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

This is an input validation vulnerability in the web-based management interface of Cisco Small Business RV042, RV042G, RV320, and RV325 routers. An authenticated Administrator-level attacker can send a crafted HTTP request with improperly validated input, causing the device to unexpectedly reload and result in a denial of service condition.

MitigationRestrict access to the router's web management interface to trusted networks or IP addresses to reduce exposure. Apply the Cisco firmware update when released. If no patch is available, consider network segmentation to limit administrative access.

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
    Locate the device label on the router chassis or check the web-based management interface system status page for the model number
    Affected if Model is RV042, RV042G, RV320, or RV325
  2. Check the installed firmware version
    In the router web UI, navigate to Status > System Summary or Administration > Firmware Upgrade to view the current firmware version
    Affected if Version matches any of these: 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.1.1.12, 1.3.2.02, 1.3.12.6-tm, or 1.3.12.19-tm
  3. Verify web-based management interface is enabled
    In the router web UI, go to Administration > Management and confirm the HTTP/HTTPS management access is enabled
    Affected if Web-based management interface is enabled and accessible
  4. Check if remote administrative access is permitted
    In Administration > Management, verify if remote access is allowed (HTTP/HTTPS from WAN or any IP outside the local network)
    Affected if Remote administrative access to the web interface is permitted to untrusted networks

The environment is affected if the device is an RV042, RV042G, RV320, or RV325 router running any of the listed firmware versions AND the web-based management interface is enabled with potential remote access exposure.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Restrict access to the router's web management interface to trusted networks or IP addresses to reduce exposure. Apply the Cisco firmware update when released. If no patch is available, consider network segmentation to limit administrative access.

Recommended fix Moderate confidence

Cisco Small Business RV Series firmware version as specified in the Cisco security advisory for CVE-2024-20523 (check sec.cloudapps.cisco.com for the exact fixed release)

  1. 1. Identify the exact hardware model (RV042, RV042G, RV320, or RV325) of the Cisco Small Business router in use
  2. 2. Access the router's web-based management interface using Administrator credentials
  3. 3. Navigate to the Administration or System section to check the current firmware version
  4. 4. Visit the Cisco Security Advisories page (sec.cloudapps.cisco.com) and search for CVE-2024-20523 to obtain the specific fixed firmware release
  5. 5. Download the fixed firmware version recommended in the Cisco advisory
  6. 6. Backup the router's current configuration before performing the upgrade
  7. 7. Upload and apply the fixed firmware version through the web interface or CLI
  8. 8. Verify the upgrade was successful and confirm the new firmware version
Caveat Review Cisco release notes for any configuration or feature changes between affected and fixed firmware versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rv042 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-20523 — 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-20523 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