CVE-2020-3146
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 · uneditedMultiple vulnerabilities in the web-based management interface of the Cisco RV110W Wireless-N VPN Firewall, RV130 VPN Router, RV130W Wireless-N Multifunction VPN Router, and RV215W Wireless-N VPN Router could allow an authenticated, remote attacker to execute arbitrary code on an affected device. The vulnerabilities are due to improper validation of user-supplied data in the web-based management interface. An attacker could exploit these vulnerabilities by sending malicious HTTP requests to a targeted device. A successful exploit could allow the attacker to execute arbitrary code on the underlying operating system of the affected device as a high-privilege 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 · moderate confidenceThis CVE covers multiple input validation flaws in the web-based management interface of Cisco RV110W, RV130, RV130W, and RV215W routers. An authenticated remote attacker can send malicious HTTP requests with specially crafted data to trigger arbitrary code execution on the underlying operating system with high-privilege (root) access. The vulnerabilities stem from the devices failing to properly sanitize user-supplied input in HTTP requests processed by the web interface.
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< 1.2.2.8< 1.0.3.55< 1.0.3.55< 1.3.1.7CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelAccess the device web interface or CLI and determine the exact model number (RV110W, RV130, RV130W, or RV215W)Affected if Model is one of RV110W, RV130, RV130W, or RV215W
-
Check RV110W firmware versionFor RV110W models: navigate to Status > System Summary in the web interface or use 'show version' via CLI; verify the firmware version is below 1.2.2.8Affected if Firmware version is lower than 1.2.2.8
-
Check RV130/RV130W firmware versionFor RV130 or RV130W models: navigate to Status > System Summary in the web interface or use 'show version' via CLI; verify the firmware version is below 1.0.3.55Affected if Firmware version is lower than 1.0.3.55
-
Check RV215W firmware versionFor RV215W models: navigate to Status > System Summary in the web interface or use 'show version' via CLI; verify the firmware version is below 1.3.1.7Affected if Firmware version is lower than 1.3.1.7
-
Verify web management interface exposureDetermine if the web-based management interface is accessible from the network (check Administration > Management Interface > Access Settings for HTTP/HTTPS remote access)Affected if Web management interface is enabled and accessible from untrusted networks
-
Check for compromise indicatorsReview system logs for unexpected configuration changes, new user accounts, or unusual HTTP request patterns to the management interfaceAffected if Logs show unauthorized configuration changes or suspicious HTTP requests to the web interface
The device is likely affected if it is an RV110W, RV130, RV130W, or RV215W model running firmware below the respective threshold versions and has its web management interface exposed to the network.
Generated from the published advisory. Verify against your own configuration.
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 data1.0.3.551.2.2.81.3.1.7
Apply the relevant Cisco firmware updates for these router models. If patches are unavailable due to end-of-life status, consider network segmentation to limit exposure and monitor for Indicators of Compromise, or replace with supported hardware.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3146 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-3146 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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