dbcve.org
Small Business Rv340 FirmwareOperating system · Cisco

CVE-2017-6784

MEDIUM · 5.3 CVSS v3.0 Published 2017-08-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
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 interface of the Cisco RV340, RV345, and RV345P Dual WAN Gigabit VPN Routers could allow an unauthenticated, remote attacker to access sensitive data. The attacker could use this information to conduct additional reconnaissance attacks. The vulnerability is due to Cisco WebEx Meetings not sufficiently protecting sensitive data when responding to an HTTP request to the web interface. An attacker could exploit the vulnerability by attempting to use the HTTP protocol and looking at the data in the HTTP responses from the Cisco WebEx Meetings Server. An exploit could allow the attacker to find sensitive information about the application. Cisco Bug IDs: CSCve37988. Known Affected Releases: firmware 1.0.0.30, 1.0.0.33, 1.0.1.9, 1.0.1.16.

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 · moderate confidence

An information disclosure vulnerability in the web interface of Cisco RV340, RV345, and RV345P VPN routers allows unauthenticated remote attackers to retrieve sensitive data via HTTP responses. The flaw exists in the Cisco WebEx Meetings component, which does not adequately protect sensitive information in its HTTP responses.

MitigationApply firmware updates provided by Cisco to address CSCve37988. Until then, restrict web interface access to trusted networks or disable the WebEx Meetings feature if possible.

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
Small Business Rv340 FirmwareOperating system
Affected:= 1.0.0.30= 1.0.0.33= 1.0.1.9= 1.0.1.16
Small Business Rv345 FirmwareOperating system
Affected:= 1.0.0.30= 1.0.0.33= 1.0.1.9= 1.0.1.16
Small Business Rv345p FirmwareOperating system
Affected:= 1.0.0.30= 1.0.0.33= 1.0.1.9= 1.0.1.16

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
Low
Integrity
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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. Check the router firmware version
    Log into the Cisco RV340/RV345/RV345P web interface and navigate to Administration > Firmware Upgrade, or use the CLI command 'show version' to display the installed firmware version.
    Affected if The displayed firmware version is exactly 1.0.0.30, 1.0.0.33, 1.0.1.9, or 1.0.1.16
  2. Identify if the WebEx Meetings component is present
    Attempt to access the router web interface and look for the WebEx Meetings feature or module. This may appear in the web interface navigation or in the URL path related to meetings or conferencing features.
    Affected if The WebEx Meetings component or feature is present and accessible on the device web interface
  3. Test for unauthenticated HTTP access to WebEx endpoints
    Send an HTTP request to common WebEx-related paths on the router (such as /webex/ or similar endpoints) without providing any authentication credentials and observe the HTTP response.
    Affected if The router returns sensitive information in HTTP responses without requiring authentication

A user is affected if the router runs one of the listed firmware versions (1.0.0.30, 1.0.0.33, 1.0.1.9, or 1.0.1.16) and the WebEx Meetings component is accessible, allowing unauthenticated retrieval of sensitive data via HTTP.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply firmware updates provided by Cisco to address CSCve37988. Until then, restrict web interface access to trusted networks or disable the WebEx Meetings feature if possible.

Fix this in Small Business Rv340 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-6784 — 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-2017-6784 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