Rv320 FirmwareOperating system · Cisco
CVE-2019-1652
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 Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers could allow an authenticated, remote attacker with administrative privileges on an affected device to execute arbitrary commands. The vulnerability is due to improper validation of user-supplied input. An attacker could exploit this vulnerability by sending malicious HTTP POST requests to the web-based management interface of an affected device. A successful exploit could allow the attacker to execute arbitrary commands on the underlying Linux shell as root. Cisco has released firmware updates that address this vulnerability.
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 confidenceThe vulnerability is a command injection flaw in the web-based management interface of Cisco RV320 and RV325 VPN routers. An attacker with administrative credentials can send specially crafted HTTP POST requests containing malicious input that is not properly validated, allowing arbitrary Linux shell commands to be executed with root privileges.
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
Rv320 FirmwareOperating system
>= 1.4.2.15, < 1.4.2.22
Rv325 FirmwareOperating system
>= 1.4.2.15, < 1.4.2.22CVSS 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 router model and firmware versionAccess the Cisco RV320 or RV325 web management interface and navigate to the Status or Administration section to view the firmware version. Alternatively, log into the router via CLI and use commands like 'show version' or check the firmware file name displayed in the web interface.Affected if The firmware version falls within the range >= 1.4.2.15 and < 1.4.2.22
-
Confirm web-based management interface is enabledCheck if the HTTP/HTTPS web interface is accessible on the router. This is typically on port 80 or 443. Verify the service is running via the router's administration panel or by attempting to access the login page.Affected if The web-based management interface is enabled and accessible, as this is required for the command injection to be exploitable
-
Verify administrative access controlsReview the router's access control settings to determine if the administrative interface is exposed to untrusted networks. Check for IP access lists, management VLAN settings, or firewall rules that restrict admin access.Affected if The administrative interface is exposed to untrusted or external networks, increasing the likelihood of exploitation
-
Inspect for signs of compromiseReview router logs for suspicious HTTP POST requests, especially those containing shell metacharacters (such as ;, |, &, $) or unusual command patterns. Check for unexpected new user accounts, unknown processes, or modified configurations.Affected if Log analysis reveals anomalous HTTP POST requests or evidence of unauthorized command execution on the device
A user is affected if they are running Cisco RV320 or RV325 firmware version 1.4.2.15 through 1.4.2.21 with the web-based management interface enabled and accessible.
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.
dbcve · scoped1.4.2.22
Apply the Cisco firmware updates that address this vulnerability. Organizations should identify affected devices, review administrative access controls, and consider network segmentation to limit exposure to authenticated attackers.
Firmware version 1.4.2.22 or later
- Download the firmware version 1.4.2.22 or later from Cisco's official support website for your specific model (RV320 or RV325)
- Log in to the router's web-based management interface with administrative credentials
- Navigate to the Administration section or Firmware Upgrade page
- Upload the downloaded firmware file
- Wait for the firmware upload and installation to complete
- The router will automatically reboot; do not power off the device during the upgrade process
- After reboot, verify the firmware version has been updated to 1.4.2.22 or later in the system status page
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Rv320 Firmware
Exploited in the wild — priority engagement
- 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-1652 — 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-1652 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