Rv016 Multi Wan Vpn Router FirmwareOperating system · Cisco

CVE-2021-1323

HIGH · 7.2 CVSS v3.1 Published 2021-02-04
Fix available
A fix is available. Upgrade to after 4.2.3.14 or later.
See remediation →
78/100
Remediation priority · High
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
Multiple vulnerabilities in the web-based management interface of Cisco Small Business RV016, RV042, RV042G, RV082, RV320, and RV325 Routers could allow an authenticated, remote attacker to execute arbitrary code or cause an affected device to restart unexpectedly. These vulnerabilities are due to improper validation of user-supplied input in the web-based management interface. An attacker could exploit these vulnerabilities by sending crafted HTTP requests to an affected device. A successful exploit could allow the attacker to execute arbitrary code as the root user on the underlying operating system or cause the device to reload, resulting in a denial of service (DoS) condition. To exploit these vulnerabilities, an attacker would need to have valid administrator credentials on the affected device.

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

Multiple input validation vulnerabilities in the web-based management interface of Cisco Small Business RV series routers allow authenticated attackers to send crafted HTTP requests and either execute arbitrary code with root privileges on the underlying OS or cause an unexpected device reload resulting in denial of service.

MitigationApply the vendor-supplied firmware patch from Cisco. Since administrator credentials are required for exploitation, immediately rotate all admin passwords and review/administrative accounts for any unauthorized changes. Consider network segmentation to limit management interface exposure.

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
Rv016 Multi Wan Vpn Router FirmwareOperating system
Affected:<= 4.2.3.14
Rv042 Dual Wan Vpn Router FirmwareOperating system
Affected:<= 4.2.3.14
Rv042g Dual Gigabit Wan Vpn Router FirmwareOperating system
Affected:<= 4.2.3.14
Rv082 Dual Wan Vpn Router FirmwareOperating system
Affected:<= 4.2.3.14
Rv320 Dual Gigabit Wan Vpn Router FirmwareOperating system
Affected:<= 1.5.1.11
Rv325 Dual Gigabit Wan Vpn Router FirmwareOperating system
Affected:<= 1.5.1.11

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
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 checks

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

  1. Identify the router model
    Access the device's web management interface and locate the System Summary or Status page, or use the command line interface (CLI) and run 'show version' to display the hardware model name (e.g., RV016, RV042, RV042g, RV082, RV320, or RV325).
    Affected if The model is one of the six affected models: RV016, RV042, RV042g, RV082, RV320, or RV325.
  2. Check the installed firmware version
    In the web interface, go to System Summary or Administration > Firmware Upgrade to view the current firmware version. Alternatively, via CLI run 'show version' which displays the firmware build number.
    Affected if The firmware version is at or below 4.2.3.14 (for RV016, RV042, RV042g, RV082) or at or below 1.5.1.11 (for RV320, RV325).
  3. Verify if web-based management interface is enabled
    In the web interface, navigate to Administration > Management or Security > Access Rules to confirm whether the HTTP/HTTPS management interface is enabled. Check which interfaces (LAN, WAN, or both) have management access permitted.
    Affected if The web-based management interface is enabled, particularly if it is accessible from the WAN interface.
  4. Review administrator accounts for unauthorized changes
    In the web interface, go to Administration > User Accounts or AAA > Users to list all configured administrative accounts. Compare against known, documented accounts and look for any unfamiliar usernames, especially those with privilege level 15 (full admin).
    Affected if There are unexpected or unauthorized administrator accounts present, or if existing accounts have altered privilege levels.
  5. Check for unexpected system changes or processes
    If CLI access is available, run 'show processes' or 'show system status' to look for unfamiliar processes. Review system logs (/var/log/messages or via the web interface Logs) for suspicious HTTP requests, particularly to CGI endpoints or unusual command injection patterns.
    Affected if There are unexpected processes, unexplained configuration changes, or suspicious log entries indicating arbitrary code execution attempts.

A user is affected if they are running any of the six listed router models with firmware at or below the specified version limits and the web management interface is enabled, especially if admin accounts have been modified without authorization.

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
Upgrade available Upgrade to a release after 4.2.3.14
Interim mitigation

Apply the vendor-supplied firmware patch from Cisco. Since administrator credentials are required for exploitation, immediately rotate all admin passwords and review/administrative accounts for any unauthorized changes. Consider network segmentation to limit management interface exposure.

Fix this in Rv016 Multi Wan Vpn Router Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-1323 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-1323 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