dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 May 2022.
Rv320 FirmwareOperating system · Cisco

CVE-2019-1653

HIGH · 7.5 CVSS v3.1 Published 2019-01-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
In the wild High EPSS Public exploit Remotely reachable No privileges Zero-click

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 · unedited
A vulnerability in the web-based management interface of Cisco Small Business RV320 and RV325 Dual Gigabit WAN VPN Routers could allow an unauthenticated, remote attacker to retrieve sensitive information. The vulnerability is due to improper access controls for URLs. An attacker could exploit this vulnerability by connecting to an affected device via HTTP or HTTPS and requesting specific URLs. A successful exploit could allow the attacker to download the router configuration or detailed diagnostic information. 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 confidence

The Cisco RV320 and RV325 routers contain an information disclosure vulnerability in their web-based management interface. Improper access controls on specific URLs allow unauthenticated remote attackers to download the router configuration file and detailed diagnostic information by sending HTTP or HTTPS requests to the device.

MitigationApply the vendor firmware update released by Cisco to address this vulnerability. If patching is not immediately possible, restrict access to the management interface to trusted networks or disable remote management if not required.

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
Affected:= 1.4.2.15= 1.4.2.17
Rv325 FirmwareOperating system
Affected:= 1.4.2.15= 1.4.2.17

CVSS 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
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the router firmware version
    Log into the router web interface and navigate to Administration > Firmware Upgrade, or use the CLI command 'show version' via SSH/Telnet to retrieve the installed firmware version
    Affected if The firmware version displayed is 1.4.2.15 or 1.4.2.17
  2. Verify remote management is enabled
    In the web interface, go to VPN > Remote Management or Administration > Remote Management to check if HTTP or HTTPS remote access is enabled for external interfaces
    Affected if Remote management via HTTP or HTTPS is enabled on any WAN-facing interface
  3. Determine if the device is internet-facing
    Check your network firewall or NAT rules to see if TCP ports 80 (HTTP) or 443 (HTTPS) are forwarded to the router's WAN IP, or attempt to access the router's public IP from an external network
    Affected if The router's management interface is reachable from untrusted networks or the public internet
  4. Confirm the device model
    Check the router label or web interface (typically at the top of the status page) to confirm the exact model is RV320 or RV325
    Affected if The device is a Cisco RV320 or RV325 router running the affected firmware versions

A user is affected if they are running Cisco RV320 or RV325 firmware version 1.4.2.15 or 1.4.2.17 with remote management enabled and accessible from untrusted networks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor firmware update released by Cisco to address this vulnerability. If patching is not immediately possible, restrict access to the management interface to trusted networks or disable remote management if not required.

Recommended fix Moderate confidence

Upgrade to the latest available firmware version for Cisco RV320/RV325 (version higher than 1.4.2.17) from Cisco's official support website

  1. 1. Identify the exact model (RV320 or RV325) of the Cisco Small Business router in your environment.
  2. 2. Access the Cisco support website (www.cisco.com) and navigate to the product pages for RV320 or RV325 routers.
  3. 3. Locate and download the latest available firmware version for your specific model. The fixed version will be greater than 1.4.2.17.
  4. 4. Access the router's web-based management interface.
  5. 5. Navigate to the Administration or System Management section.
  6. 6. Locate the firmware upgrade option and upload the downloaded firmware file.
  7. 7. Wait for the upgrade process to complete and the router to reboot.
  8. 8. After reboot, verify the firmware version in the management interface to confirm the upgrade was successful.
Caveat Review Cisco release notes for any configuration changes required after firmware upgrade

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
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-1653 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-1653 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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