dbcve.org
Prime InfrastructureApplication · Cisco

CVE-2017-6782

MEDIUM · 5.4 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 →
58/100
Remediation priority · Elevated
Remotely reachable

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 administrative web interface of Cisco Prime Infrastructure could allow an authenticated, remote attacker to modify a page in the web interface of the affected application. The vulnerability is due to improper sanitization of parameter values by the affected application. An attacker could exploit this vulnerability by injecting malicious code into an affected parameter and persuading a user to access a web page that triggers the rendering of the injected code. Cisco Bug IDs: CSCve47074. Known Affected Releases: 3.2(0.0).

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 Cross-Site Scripting (XSS) vulnerability in Cisco Prime Infrastructure's administrative web interface. An authenticated attacker can inject malicious JavaScript code into parameter values that are not properly sanitized. When other users access pages rendering the injected code, it executes in their browsers, potentially allowing session hijacking, credential theft, or defacement.

MitigationApply the Cisco patch for bug CSCve47074 (upgrade to patched release). Implement input validation and output encoding on affected parameters, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

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:= 3.2\(0.0\)

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.0/AV:N/AC:L/PR:L/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 the installed Cisco Prime Infrastructure version
    Log into the administrative web interface and navigate to the About or Version page, typically found under Administration > Settings or Help > About. Alternatively, check the version displayed on the login page or in the system dashboard.
    Affected if The version displayed equals exactly 3.2(0.0)
  2. Confirm the administrative web interface is accessible
    Verify that the Cisco Prime Infrastructure web interface (HTTPS on port 443 or 8443 by default) is reachable and responsive.
    Affected if The web interface is exposed and responds to HTTP/HTTPS requests
  3. Review web server logs for suspicious parameter patterns
    Examine access logs (typically located in /opt/CSU-logs or similar application log directories) for the web server. Search for unusual characters in parameter values such as <script>, javascript:, onerror=, or other HTML/script tags in URL parameters.
    Affected if Logs contain requests with unescaped HTML or JavaScript characters in parameter values that were processed by the application
  4. Check for indicators of successful XSS exploitation
    Review browser console logs or security monitoring tools for alerts related to XSS events. Look for unexpected script executions or CSP violations if CSP is configured.
    Affected if Evidence exists of script execution from unexpected sources or parameter values appearing in rendered pages without encoding

You are affected if your Cisco Prime Infrastructure version is exactly 3.2(0.0) and the administrative web interface is accessible, with potential exploitation indicated by suspicious patterns in web logs or unexpected script execution evidence.

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 Cisco patch for bug CSCve47074 (upgrade to patched release). Implement input validation and output encoding on affected parameters, and consider deploying Content Security Policy (CSP) headers to mitigate XSS execution.

Fix this in Prime Infrastructure Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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