dbcve.org
Evolved Programmable Network ManagerApplication · Cisco

CVE-2017-6699

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 reflected cross-site scripting (XSS) attack against a user of the web-based management interface of an affected device. More Information: CSCvc24616 CSCvc35363 CSCvc49574. 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 · moderate confidence

Reflected cross-site scripting (XSS) vulnerability in the web-based management interface of Cisco Prime Infrastructure (PI) and Evolved Programmable Network Manager (EPNM). An unauthenticated, remote attacker can inject malicious script through the interface that gets reflected back to users, potentially stealing session cookies or performing actions on behalf of authenticated users.

MitigationApply the relevant Cisco security updates from CSCvc24616, CSCvc35363, or CSCvc49574 for the affected releases (3.1(1), 2.0(4.0.45B)). If patches are unavailable, consider restricting web management interface access to trusted networks or implementing WAF rules to filter malicious input.

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
Evolved Programmable Network ManagerApplication
Affected:= 2.0\(4.0.45b\)= 2.0\(4.0.45d\)= 2.0.0
Prime InfrastructureApplication
Affected:= 3.1= 3.1\(0.128\)= 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 Cisco PI or EPNM installation
    Check system inventory, running processes, or installed software listings for 'Cisco Prime Infrastructure' or 'Evolved Programmable Network Manager' products
    Affected if The product is Cisco Prime Infrastructure or Cisco Evolved Programmable Network Manager
  2. Determine installed version
    Access the web management interface and navigate to the About or Version page, or use the CLI command 'show version' if available, to retrieve the exact version number
    Affected if The version matches 3.1, 3.1(0.128), 3.1.1 for Prime Infrastructure OR 2.0(4.0.45b), 2.0(4.0.45d), 2.0.0 for EPNM
  3. Verify web management interface is accessible
    Attempt to reach the web-based management interface via HTTP/HTTPS on the management IP address or hostname
    Affected if The web interface responds and is reachable over the network
  4. Check interface exposure
    Review network accessibility settings, firewall rules, or ACLs to determine if the web management interface is exposed to untrusted networks or the internet
    Affected if The interface is exposed to untrusted networks or external attackers

A user is affected if they have Cisco Prime Infrastructure version 3.1/3.1(0.128)/3.1.1 or EPNM version 2.0(4.0.45b)/2.0(4.0.45d)/2.0.0 deployed with the web management interface accessible to potential attackers

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 the relevant Cisco security updates from CSCvc24616, CSCvc35363, or CSCvc49574 for the affected releases (3.1(1), 2.0(4.0.45B)). If patches are unavailable, consider restricting web management interface access to trusted networks or implementing WAF rules to filter malicious input.

Fix this in Evolved Programmable Network Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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