Prime InfrastructureApplication · Cisco
CVE-2017-6724
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 · uneditedA vulnerability in the web framework code of Cisco Prime Infrastructure could allow an unauthenticated, remote attacker to conduct a cross-site scripting (XSS) attack against a user of the web interface of an affected system. More Information: CSCuw65843. Known Affected Releases: 3.1(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 confidenceCross-site scripting (XSS) vulnerability in Cisco Prime Infrastructure's web framework allows unauthenticated remote attackers to inject malicious scripts into the web interface. The vulnerability is exploitable without authentication, requiring user interaction (such as clicking a crafted link) to execute the attack.
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
= 3.1\(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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Cisco Prime Infrastructure installationCheck if Cisco Prime Infrastructure is installed on the system by looking for the installation directory (typically /opt/cpim or checking for the 'Prime Infrastructure' service) or by querying running processes for 'prime' or 'cpim' processes.Affected if The system has Cisco Prime Infrastructure installed and running.
-
Determine the installed versionAccess the Cisco Prime Infrastructure web interface and navigate to the About page, or check the version file in the installation directory (often found in /opt/cpim/version or via CLI: 'show version' in the Prime Infrastructure console).Affected if The installed version is exactly 3.1(0.0).
-
Verify web interface accessibilityAttempt to access the Cisco Prime Infrastructure login page via HTTP/HTTPS (default ports 8080 or 443) from the network. Check if the web interface responds to requests.Affected if The web interface is exposed and accessible over the network.
-
Confirm unauthenticated access to web frameworkTest accessing web application endpoints without credentials. The vulnerability allows unauthenticated attackers to inject scripts, so verify whether the login page or other public endpoints accept input that could contain script tags.Affected if The web interface permits unauthenticated access and accepts user input without sanitization.
A system is affected if Cisco Prime Infrastructure version 3.1(0.0) is installed with its web interface accessible to unauthenticated users, allowing potential XSS injection via unsanitized input.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor patch for CSCuw65843; in the interim, disable the web interface or restrict network access to trusted users only to reduce exposure.
Fix this in Prime Infrastructure
Scoped from the published advisory
- Consultation6.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-6724 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-6724 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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