dbcve.org
Rv042 FirmwareOperating system · Cisco

CVE-2024-20520

CRITICAL · 9.1 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 →
97/100
Remediation priority · Urgent
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 execute arbitrary code as the root user. 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-supplied input in the web-based management interface. An attacker could exploit this vulnerability by sending crafted HTTP requests to an affected device. A successful exploit could allow the attacker to execute arbitrary code on the underlying operating system as the root user.

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

Authenticated RCE vulnerability in Cisco Small Business RV042/RV042G/RV320/RV325 router web management interface. Improper validation of user-supplied input allows an attacker with Administrator credentials to execute arbitrary code as root user on the underlying OS via crafted HTTP requests.

MitigationRestrict web management interface access to trusted networks only; apply Cisco firmware updates when available; enforce strong Administrator credentials and monitor for anomalous HTTP requests.

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
High
Integrity
High
Availability
High

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

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

  1. Identify router model
    Access the web-based management interface and check the device model in the Status or System Summary page, or inspect the physical device label
    Affected if Model is RV042, RV042G, RV320, or RV325
  2. Check firmware version
    In the web interface, navigate to Status > System Summary or similar to view the firmware version. The version is typically displayed as a string like 1.3.1.10
    Affected if Router model is one of the affected models
  3. Compare version to affected list
    Compare your installed firmware version against these 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, 1.3.12.19-tm
    Affected if Installed firmware version exactly matches one of the listed versions
  4. Verify web management interface is enabled
    Check if the HTTP/HTTPS web management interface is accessible by navigating to the router's IP address in a browser
    Affected if Web interface is accessible and you can reach the login page
  5. Confirm Administrator access exists
    Verify that Administrator-level credentials are configured or can be obtained for the device
    Affected if An Administrator account exists on the device

You are affected if you have a RV042/RV042G/RV320/RV325 router running any of the firmware versions exactly matching 1.0.1.17 through 1.3.12.19-tm, with the web management interface exposed and Administrator credentials accessible.

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 web management interface access to trusted networks only; apply Cisco firmware updates when available; enforce strong Administrator credentials and monitor for anomalous HTTP requests.

Recommended fix Moderate confidence

Fixed firmware version available from Cisco security advisory (obtain from sec.cloudapps.cisco.com)

  1. 1. Check Cisco's official security advisory for CVE-2024-20520 at sec.cloudapps.cisco.com to obtain the specific fixed firmware version
  2. 2. Identify the exact router model (RV042, RV042G, RV320, or RV325) from the affected device
  3. 3. Download the fixed firmware version from Cisco's support portal
  4. 4. Back up the current router configuration
  5. 5. Access the router's web-based management interface
  6. 6. Navigate to the Administration or System Management section
  7. 7. Use the firmware update functionality to upload and install the fixed firmware version
  8. 8. After reboot, verify the firmware version matches the fixed release
Caveat Review Cisco release notes for the fixed version for any configuration or compatibility changes

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

Fix this in Rv042 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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