Prime InfrastructureApplication · Cisco
CVE-2017-3848
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 HTTP web-based management interface 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 the affected system. More Information: CSCuw63001 CSCuw63003. Known Affected Releases: 2.2(2). Known Fixed 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 HTTP web-based management interface allows unauthenticated remote attackers to inject malicious scripts that execute in the browsers of legitimate users accessing the compromised web interface.
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
= 2.2\(2\)= 3.0CVSS 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.
-
Confirm Cisco Prime Infrastructure is presentIdentify if Cisco Prime Infrastructure is installed in your environment by checking for the application in your system inventory, or by accessing the web login page at the HTTP/HTTPS endpoint used for Cisco Prime Infrastructure management.Affected if Cisco Prime Infrastructure is not installed or not accessible via web interface
-
Determine the installed versionLog into the Cisco Prime Infrastructure web interface as an administrator and navigate to the 'About' page typically found under the Help or Administration menu, or check the version displayed on the login page. Alternatively, check the version via CLI if you have direct server access.Affected if Unable to determine version from interface or system
-
Compare version against vulnerable releasesReview the identified version number. The vulnerable versions are exactly 2.2(2) and exactly 3.0. Note that other versions (including 3.1 and later) are not affected by this specific CVE.Affected if The installed version is exactly 2.2(2) or exactly 3.0
-
Verify HTTP web interface is accessibleAttempt to access the Cisco Prime Infrastructure login page over HTTP (port 80) or HTTPS (port 443) at the management URL. Confirm the interface responds and is reachable.Affected if The HTTP web-based management interface is not accessible or not in use
You are affected if Cisco Prime Infrastructure version 2.2(2) or 3.0 is installed and the HTTP web-based management interface is accessible.
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 dataUpgrade to Cisco Prime Infrastructure version 3.1(0.0) or later. Until upgrade is possible, consider disabling HTTP web-based management or deploying WAF rules to filter malicious requests.
Fix this in Prime Infrastructure
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3848 — 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-3848 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