Rv110w FirmwareOperating system · Cisco
CVE-2021-1161
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 Cisco Small Business RV110W, RV130, RV130W, and RV215W Routers could allow an authenticated, remote attacker to execute arbitrary code or cause an affected device to restart unexpectedly. The 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. Cisco has not released software updates that address these vulnerabilities.
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 input validation vulnerabilities in the web-based management interface of Cisco Small Business RV110W, RV130, RV130W, and RV215W routers allow authenticated remote attackers to execute arbitrary code as root or cause device reload (DoS) via crafted HTTP requests. The attacker needs valid administrator credentials.
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= 1.3.1.7
Rv130 Vpn Router FirmwareOperating system
= 1.2.2.8= 1.3.1.7
Rv130w FirmwareOperating system
= 1.2.2.8= 1.3.1.7
Rv215w Wireless N Vpn Router FirmwareOperating system
= 1.2.2.8= 1.3.1.7
Application Extension PlatformPlugin / extension
= 1.0.3.55CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelAccess the device management interface and locate the model information, typically found in Status, System Info, or Device Information pages. For CLI, use 'show version' or similar commands.Affected if Device is not one of the following models: RV110W, RV130, RV130W, RV215W, or Cisco Application Extension Platform (AXP)
-
Check the router firmware versionIn the web management interface, navigate to Administration, System, or Status pages to view the firmware version. For CLI access, use 'show version' or 'cat /proc/version' if available.Affected if Firmware version is exactly 1.2.2.8 or exactly 1.3.1.7 on RV110W, RV130, RV130W, or RV215W routers
-
Check the AXP firmware versionIf the device is a Cisco Application Extension Platform, locate the version in its management interface under System or Status sections.Affected if AXP firmware version is exactly 1.0.3.55
-
Confirm web-based management is enabledCheck the device configuration for HTTP/HTTPS management interface settings, typically under Administration, Management, or Access Settings. Verify if the interface is accessible.Affected if Web-based management interface is enabled and accessible to the attacker network segment
-
Assess management interface exposureReview firewall rules, WAN access settings, or ACLs that control access to the web management interface. Check if it is reachable from untrusted networks.Affected if Management interface is exposed to untrusted networks or the attacker can obtain valid administrator credentials through other means
The device is vulnerable only if it is an RV110W, RV130, RV130W, or RV215W router with firmware exactly 1.2.2.8 or 1.3.1.7 (or AXP with 1.0.3.55), AND the web-based management interface is accessible to the attacker who has valid administrator credentials.
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 dataSince Cisco has not released patches, mitigation requires either replacing affected routers with supported models or strictly limiting management interface access to trusted networks/hosts only, ideally behind a VPN or ACL-protected jump host.
Fix this in Rv110w Firmware
Scoped from the published advisory
- Consultation8.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $10,240.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1161 — 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-2021-1161 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