Rv110w FirmwareOperating system · Cisco
CVE-2020-3145
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 · high confidenceMultiple vulnerabilities in Cisco RV series wireless VPN routers (RV110W, RV130, RV130W, RV215W) allow an authenticated remote attacker to execute arbitrary code on the underlying OS by sending malicious HTTP requests to the web-based management interface. The root cause is improper validation of user-supplied data in 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
Rv110w FirmwareOperating system
< 1.2.2.8
Rv130 FirmwareOperating system
< 1.0.3.55
Rv130w FirmwareOperating system
< 1.0.3.55
Rv215w FirmwareOperating system
< 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 the router modelLog into the device web interface or check the physical device label to determine if it is one of RV110W, RV130, RV130W, or RV215WAffected if The device is one of the four affected models (RV110W, RV130, RV130W, RV215W)
-
Check the installed firmware versionAccess the router web interface and navigate to the Status or Administration section to view the firmware version. Alternatively, use the command line or check the device documentation for the version display methodAffected if The firmware version is below 1.2.2.8 for RV110W, below 1.0.3.55 for RV130/RV130W, or below 1.3.1.7 for RV215W
-
Verify if the web-based management interface is enabledCheck the router security settings for HTTP/HTTPS management access configuration. Look for options such as 'Web Management', 'HTTP Management', or 'Remote Management' in the web interface under Administration or Security settingsAffected if The web-based management interface is enabled and accessible
-
Check if remote management access is permittedIn the router web interface, locate the management access settings and determine if remote (WAN) access to the web interface is allowed, or if only local (LAN) access is permittedAffected if Remote management access is enabled, allowing HTTP requests from outside the local network
A user is affected if they own an RV110W, RV130, RV130W, or RV215W router running firmware below the specified version thresholds AND the web-based management interface is accessible (especially if remote management is enabled).
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 vendor-supplied firmware update for the affected Cisco RV series routers. If no update is available, restrict web-based management interface access to trusted IP addresses or disable remote management entirely.
Fix this in Rv110w Firmware
Scoped from the published advisory
- Consultation4.0 h
- Implementation3.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,680.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-3145 — 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-3145 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