dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2017-6700

MEDIUM · 6.1 CVSS v3.0 Published 2017-07-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Prime Infrastructure (PI) and Evolved Programmable Network Manager (EPNM) could allow an unauthenticated, remote attacker to conduct a Document Object Model (DOM) based (environment or client-side) cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. More Information: CSCvc24620 CSCvc49586. Known Affected Releases: 3.1(1) 2.0(4.0.45B).

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

This is a DOM-based (client-side) cross-site scripting vulnerability in Cisco Prime Infrastructure and Evolved Programmable Network Manager web management interfaces. An unauthenticated remote attacker can craft malicious URLs that, when clicked by an authenticated administrator, execute arbitrary JavaScript in their browser within the context of the vulnerable application.

MitigationApply available vendor patches/updates from Cisco for PI and EPNM. As an interim control, consider disabling the web-based management interface if not required, or deploy a WAF to filter malicious requests.

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
Prime InfrastructureApplication
Affected:= 2.0\(4.0.45b\)= 3.1\(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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 if Cisco Prime Infrastructure or EPNM is installed
    Check for the presence of the Cisco PI/EPNM web management interface by accessing the login page at your application's base URL (typically https://your-server/). Look for Cisco branding or check server processes for 'prime' or 'EPNM' related services.
    Affected if The product is Cisco Prime Infrastructure or Evolved Programmable Network Manager running the web management interface.
  2. Determine the installed version of Cisco Prime Infrastructure
    Log into the Prime Infrastructure web interface and navigate to Home > Dashboard, or check the footer of any web page for the version string. Alternatively, access the server via SSH and run: show version or check /opt/CSU/etc/version if accessible.
    Affected if The version displayed is 2.0(4.0.45b) or 3.1(1).
  3. Determine the installed version of EPNM
    Log into the EPNM web interface and check the version displayed on the login page or within the admin dashboard. Alternatively, access the server via SSH and check for EPNM-specific version files or run: show version.
    Affected if The EPNM version matches the affected Prime Infrastructure versions listed (2.0(4.0.45b) or 3.1(1)).
  4. Verify the web management interface is enabled
    Confirm the web-based management interface is active and accessible by attempting to reach the login page. Check if HTTP/HTTPS services are listening on the server (e.g., netstat -an | grep -E '80|443' or similar).
    Affected if The web management interface is accessible and responding to requests.
  5. Inspect URL handling for potential DOM XSS vectors
    Review web application logs or proxy logs for suspicious URL patterns containing JavaScript handlers in query parameters. Common DOM XSS sinks include document.location, innerHTML, or eval() with URL-derived data.
    Affected if The application processes URL parameters without proper sanitization and reflects them in the response without encoding.

You are affected if Cisco Prime Infrastructure or EPNM version 2.0(4.0.45b) or 3.1(1) is running with the web management interface enabled, as the vulnerability allows injected JavaScript execution via malicious URLs.

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 available vendor patches/updates from Cisco for PI and EPNM. As an interim control, consider disabling the web-based management interface if not required, or deploy a WAF to filter malicious requests.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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