dbcve.org
Cisco Prime HomeApplication · Cisco

CVE-2017-3791

CRITICAL · 10.0 CVSS v3.0 Published 2017-02-01
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
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 GUI of Cisco Prime Home could allow an unauthenticated, remote attacker to bypass authentication and execute actions with administrator privileges. The vulnerability is due to a processing error in the role-based access control (RBAC) of URLs. An attacker could exploit this vulnerability by sending API commands via HTTP to a particular URL without prior authentication. An exploit could allow the attacker to perform any actions in Cisco Prime Home with administrator privileges. This vulnerability affects Cisco Prime Home versions from 6.3.0.0 to the first fixed release 6.5.0.1. Cisco has released software updates that address this vulnerability. There are no workarounds that address this vulnerability. Cisco Bug IDs: CSCvb49837.

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

A vulnerability in Cisco Prime Home's web-based GUI allows unauthenticated remote attackers to bypass role-based access control (RBAC) checks on specific URLs, enabling them to send API commands and execute actions with full administrator privileges without any authentication.

MitigationUpgrade Cisco Prime Home to version 6.5.0.1 or later. No workarounds are available for this authentication bypass vulnerability.

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
Cisco Prime HomeApplication
Affected:= 6.3.0.0= 6.3.1.0= 6.4.0.0= 6.4.1.0= 6.4.2.0= 6.4.2.1

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

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

  1. Identify if Cisco Prime Home is installed
    Look for Cisco Prime Home installation directories or check running services on the system. Common paths include /opt/cisco/primehome or check for processes named 'PrimeHome' or 'ciscoPrimeHome'.
    Affected if The software is present on the system.
  2. Determine the installed version
    Check the version of Cisco Prime Home installed. Typically found in an About page in the web GUI, or check version files in the installation directory such as VERSION.txt, build.properties, or similar version metadata files.
    Affected if The installed version matches 6.3.0.0, 6.3.1.0, 6.4.0.0, 6.4.1.0, 6.4.2.0, or 6.4.2.1.
  3. Verify web interface accessibility
    Determine if the Cisco Prime Home web interface is accessible from network locations. Check firewall rules and listening services on ports typically used by the application (commonly 80, 443, or 8080).
    Affected if The web interface is externally accessible or accessible from untrusted networks.
  4. Inspect for unauthorized administrative actions
    Review system logs, audit logs, and access logs for any API commands or administrative actions performed without corresponding successful authentication events. Look for requests to administrative API endpoints that lack proper authentication tokens.
    Affected if Administrative actions appear in logs without prior authentication events.

A user is affected if Cisco Prime Home version 6.3.x, 6.4.0.x, 6.4.1.x, or 6.4.2.x is installed and its web interface is accessible.

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

Upgrade Cisco Prime Home to version 6.5.0.1 or later. No workarounds are available for this authentication bypass vulnerability.

Recommended fix High confidence

6.5.0.1 or later

  1. Identify the current Cisco Prime Home version running in the environment
  2. Schedule a maintenance window for the upgrade
  3. Back up the current Cisco Prime Home configuration and database according to standard backup procedures
  4. Download Cisco Prime Home version 6.5.0.1 or later from the Cisco software download center
  5. Execute the upgrade following Cisco's official upgrade documentation for Prime Home
  6. After upgrade completes, verify the new version is 6.5.0.1 or later by checking the web-based GUI or command line
  7. Confirm the authentication bypass vulnerability is resolved by attempting to access the API URLs without credentials (should fail)
Caveat Review Cisco release notes for 6.5.0.1 for any configuration or behavioral changes that may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Cisco Prime Home Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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