Prime Service CatalogApplication · Cisco
CVE-2017-3810
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 of Cisco Prime Service Catalog could allow an authenticated, remote attacker to conduct a web URL redirect attack against a user who is logged in to an affected system. More Information: CSCvb21745. Known Affected Releases: 10.0_R2_tanggula.
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 confidenceOpen redirect vulnerability in Cisco Prime Service Catalog's web framework allows an authenticated attacker to craft malicious URLs that redirect logged-in users to arbitrary external sites.
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 Service CatalogApplication
= 10.0\(r2\)_baseCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify Cisco Prime Service Catalog is installedCheck for the application in the system inventory or look for the installation directory (commonly under /opt/cisco/ or C:\Program Files\Cisco\ on Windows). Also check for running services related to Cisco Prime (look for processes named 'prime' or port 8080/8443 listeners if the default web ports are used).Affected if The product is present on the system
-
Determine the installed versionCheck the version of Cisco Prime Service Catalog. Common locations: the About page in the web interface, the installer logs, or a version file in the installation directory. The web interface version is typically accessible at the login page or through the Help > About menu after authentication.Affected if The version matches 10.0(r2)_base exactly
-
Confirm web interface accessibilityVerify the web interface is accessible by attempting to reach the login page (typically https://hostname:8443/ or http://hostname:8080/). The vulnerability exists in the web framework, so the web component must be running.Affected if The web interface responds and accepts authentication
-
Check for active authentication sessionsThe vulnerability requires an authenticated attacker to craft malicious redirect URLs. Review active user sessions or recent authentication logs to determine if untrusted users have access.Affected if Untrusted or low-privilege authenticated users can access the web interface
You are affected if Cisco Prime Service Catalog version 10.0(r2)_base is installed and its web interface is accessible to authenticated users, particularly untrusted or low-privilege accounts.
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 vendor patch CSCvb21745 for the affected release 10.0_R2_tanggula; alternatively, implement strict URL validation or whitelisting for redirect parameters at the application or WAF layer to block untrusted destinations.
Fix this in Prime Service Catalog
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-3810 — 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-3810 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