CVE-2021-1185
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 confidenceImproper input validation in the web-based management interface of Cisco Small Business RV110W, RV130, RV130W, and RV215W routers allows authenticated administrators to send crafted HTTP requests that can execute arbitrary code as root user or cause device reload (DoS). Cisco has not released patches as these are end-of-life devices.
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.3.1.7= 1.2.2.8= 1.3.1.7= 1.2.2.8= 1.3.1.7= 1.2.2.8= 1.3.1.7= 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 router modelLog into the web-based management interface and check the status or system information page to identify the exact model (RV110W, RV130, RV130W, or RV215W). Alternatively, check the physical device label.Affected if Model is one of RV110W, RV130, RV130W, or RV215W routers.
-
Check the firmware versionIn the web UI, navigate to Administration > Firmware Upgrade or Status > System Summary to view the installed firmware version. Compare against the affected versions: 1.2.2.8 or 1.3.1.7 for the routers.Affected if Firmware version equals 1.2.2.8 or 1.3.1.7 on any of the affected router models.
-
Identify Application Extension Platform versionIf the device is not one of the RV routers, check if the Cisco Application Extension Platform is installed. Access its management interface and locate the version information, typically under System or About sections.Affected if Application Extension Platform version equals 1.0.3.55.
-
Confirm web-based management interface is accessibleVerify that the web-based management interface is enabled and reachable on the device. This is typically accessible via HTTP/HTTPS on the LAN or WAN interface depending on configuration.Affected if The web management interface is enabled and accessible (required for the vulnerability to be exploitable).
The device is affected if it is a Cisco RV110W, RV130, RV130W, or RV215W router running firmware version 1.2.2.8 or 1.3.1.7, or a Cisco Application Extension Platform version 1.0.3.55, and the web-based management interface 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 dataSince no vendor patches exist, implement network segmentation to isolate affected routers, restrict management interface access to trusted admin IP addresses via ACLs, and plan for replacement with supported hardware; consider deploying a WAF or IPS to detect and block malicious HTTP requests.
- Consultation6.0 h
- Implementation12.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-1185 — 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-1185 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