Rv110w FirmwareOperating system · Cisco
CVE-2019-1843
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 · uneditedA vulnerability in the web-based management interface of the Cisco RV110W Wireless-N VPN Firewall, Cisco RV130W Wireless-N Multifunction VPN Router, and Cisco RV215W Wireless-N VPN Router could allow an unauthenticated, remote attacker to cause a reload of an affected device, resulting in a denial of service (DoS) condition. This vulnerability is due to improper validation of user-supplied data in the web-based management interface. An attacker could exploit this vulnerability by sending malicious HTTP requests to a targeted device. A successful exploit could allow the attacker to reload the device and causing a DoS condition.
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 confidenceThis is a denial of service vulnerability in the web-based management interface of Cisco RV110W, RV130W, and RV215W VPN routers. An unauthenticated remote attacker can exploit improper validation of user-supplied data by sending malicious HTTP requests to cause the device to reload, resulting in a DoS condition.
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.4
Rv130w FirmwareOperating system
< 1.0.3.51
Rv215w FirmwareOperating system
< 1.3.1.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 router's web-based management interface and look for the model number displayed on the status page, or check the device label on the physical router hardware.Affected if Router model is RV110W, RV130W, or RV215W.
-
Locate firmware versionIn the router web interface, navigate to the Status or System Summary page to find the firmware version displayed. Alternatively, access the router via CLI and use the 'show version' command.Affected if Firmware version cannot be determined or is visible.
-
Compare version against affected rangesMatch your firmware version to the following vulnerable ranges: RV110W < 1.2.2.4, RV130W < 1.0.3.51, RV215W < 1.3.1.4. Versions prior to these thresholds are affected.Affected if Your installed firmware version falls below the corresponding threshold for your model.
-
Verify web-based management is enabledIn the router web interface, go to Administration or Management settings and check if the web-based management interface is enabled. This is typically enabled by default on these devices.Affected if Web-based management interface is enabled (this is required for the vulnerability to be exploitable).
You are affected if you have an RV110W, RV130W, or RV215W router with firmware version below 1.2.2.4, 1.0.3.51, or 1.3.1.4 respectively, 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 data1.0.3.511.2.2.41.3.1.4
Apply the relevant Cisco firmware update for the affected router models. As an interim measure, restrict access to the web-based management interface to trusted networks or disable remote web management if not required.
Fix this in Rv110w Firmware
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-1843 — 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-2019-1843 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