Rv110w FirmwareOperating system · Cisco
CVE-2021-1194
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 RV series routers (RV110W, RV130, RV130W, RV215W) allow an authenticated attacker with admin credentials to send crafted HTTP requests that trigger arbitrary code execution as root user or cause device reload (DoS). The root cause is improper validation of user-supplied input in HTTP request handling.
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 device modelAccess the router web interface or check the physical device label to confirm the model number is one of: RV110W, RV130, RV130W, RV215W, or Cisco Application Extension Platform.Affected if The device model is any of the listed affected models.
-
Check firmware versionLog into the router web interface and navigate to Status or System Summary page to view the firmware version. Alternatively, access the device via CLI and run 'show version' or check /proc/version if accessible.Affected if The firmware version is exactly 1.2.2.8, 1.3.1.7, or 1.0.3.55.
-
Verify web-based management interface is enabledIn the router web interface, go to Administration or Management settings and confirm that HTTP or HTTPS management access is enabled.Affected if HTTP/HTTPS management interface is enabled on any interface.
-
Check remote management accessibilityDetermine if the management interface is accessible from WAN/outside networks by reviewing the 'Remote Management' or 'Access Control' settings. Confirm whether management is restricted to LAN only or exposed to WAN.Affected if Remote management is enabled and the interface is accessible from external networks.
-
Review admin account accessCheck the list of configured admin accounts in the router web interface under User Management or Administration > Users.Affected if Any admin accounts exist with privileges to access the web management interface.
A user is affected if they have a listed device model running an affected firmware version (1.2.2.8, 1.3.1.7, or 1.0.3.55) with the web-based management interface enabled and accessible, especially from untrusted networks.
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, implement compensating controls: restrict management interface access to trusted networks only (e.g., via ACLs or VPN), disable remote management if not required, monitor for suspicious HTTP activity, and consider replacing affected devices with supported models.
Fix this in Rv110w Firmware
Scoped from the published advisory
- Consultation6.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,528.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1194 — 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-1194 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