Rv016 FirmwareOperating system · Cisco

CVE-2020-3291

HIGH · 7.2 CVSS v3.1 Published 2020-06-18
Fix available
A fix is available. Upgrade to after 4.2.3.10 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 RV320 and RV325 Series Routers and Cisco Small Business RV016, RV042, and RV082 Routers could allow an authenticated, remote attacker with administrative privileges to execute arbitrary code on an affected device. The vulnerabilities are due to insufficient boundary restrictions on user-supplied input to scripts in the web-based management interface. An attacker with administrative privileges that are sufficient to log in to the web-based management interface could exploit each vulnerability by sending crafted requests that contain overly large values to an affected device, causing a stack overflow. A successful exploit could allow the attacker to cause the device to crash or allow the attacker to execute arbitrary code with root privileges on the underlying operating system.

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

Stack overflow vulnerabilities in the web-based management interface of Cisco Small Business RV320/RV325/RV016/RV042/RV082 routers allow authenticated attackers with administrative privileges to send crafted requests containing overly large values, potentially achieving arbitrary code execution with root privileges on the underlying OS.

MitigationApply Cisco's firmware updates when available; until then, restrict administrative web interface access to trusted networks or VPN connections only, and monitor for suspicious login activity.

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 FirmwareOperating system
Affected:<= 4.2.3.10
Rv042 FirmwareOperating system
Affected:<= 4.2.3.10
Rv042g FirmwareOperating system
Affected:<= 4.2.3.10
Rv082 FirmwareOperating system
Affected:<= 4.2.3.10
Rv320 FirmwareOperating system
Affected:<= 1.5.1.05
Rv325 FirmwareOperating system
Affected:<= 1.5.1.05

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 router model
    Access the router's web-based management interface or check the physical device label to confirm the exact model (RV016, RV042, RV042g, RV082, RV320, or RV325)
    Affected if The model is one of the six listed RV series routers
  2. Check firmware version
    In the router's web interface, navigate to the Status or Administration section to view the current firmware version. Compare this version against the affected ranges: RV016/RV042/RV042g/RV082 at version 4.2.3.10 or lower, or RV320/RV325 at version 1.5.1.05 or lower
    Affected if The installed firmware version falls within or below the specified version thresholds for your model
  3. Verify web-based management interface status
    Confirm whether the web-based management interface (HTTP/HTTPS) is enabled on the router. This is typically found under Administration, Access, or Security settings in the router configuration
    Affected if The web-based management interface is enabled and accessible
  4. Assess administrative access exposure
    Determine if the administrative web interface is reachable from untrusted networks. Check router firewall rules, port forwarding settings, or WAN access configurations to see if TCP ports 80/443 are exposed to the internet or untrusted LAN segments
    Affected if The administrative interface can be reached by users who do not have legitimate administrative credentials

You are affected if you are running any of the listed router models with firmware at or below the specified version thresholds and the web-based management interface is accessible to the attacker.

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.10
Interim mitigation

Apply Cisco's firmware updates when available; until then, restrict administrative web interface access to trusted networks or VPN connections only, and monitor for suspicious login activity.

Fix this in Rv016 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,790
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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