Prime Service CatalogApplication · Cisco

CVE-2015-6395

MEDIUM · 6.5 CVSS v2.0 Published 2015-12-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
Cisco Prime Service Catalog 10.0, 10.0(R2), 10.1, and 11.0 does not properly restrict access to web pages, which allows remote attackers to modify the configuration via a direct request, aka Bug ID CSCuw48188.

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

Cisco Prime Service Catalog versions 10.0 through 11.0 contains an Insecure Direct Object Reference (IDOR) vulnerability where the application fails to enforce proper authorization checks on certain web pages, allowing authenticated remote attackers to directly request and modify system configuration settings without appropriate privileges.

MitigationApply the vendor patch from Cisco for Bug ID CSCuw48188. Until patched, restrict network access to administrative interfaces via firewall rules and monitor for unauthorized configuration changes.

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
Affected:= 10.0\(r2\)_base= 10.0_base= 10.1_base= 11.0_base

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
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

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 Prime Service Catalog version
    Access the application's login page or admin interface and locate the version information, typically found in the footer, About page, or in the installation directory's version file. Alternatively, query the application's API endpoint if known.
    Affected if The installed version is 10.0 (r2), 10.0, 10.1, or 11.0_base.
  2. Verify web interface accessibility
    Determine if the Cisco Prime Service Catalog web interface (typically ports 8080, 8443, or 80/443) is exposed to network segments beyond the trusted administrative network.
    Affected if The web interface is accessible from untrusted networks or non-administrator segments.
  3. Review user session authorization
    Log in with a low-privilege user account (non-administrator) and attempt to access administrative configuration pages or URLs directly by modifying request parameters or navigating to known admin paths such as /admin, /config, or similar endpoints.
    Affected if A non-privileged user can access or modify system configuration settings without proper authorization.
  4. Inspect access logs for IDOR indicators
    Review web server and application logs for suspicious requests where object references (IDs, parameters, or paths) are directly accessed by users who should not have privileges to those resources.
    Affected if Logs show authenticated users accessing configuration endpoints outside their assigned privileges.
  5. Audit configuration changes
    Check system configuration settings, particularly administrative parameters, user permissions, or system preferences, for unauthorized or unexpected modifications.
    Affected if Configuration settings have been altered without documented administrative approval or by accounts lacking administrative rights.

A user is affected if Cisco Prime Service Catalog version 10.0 through 11.0 is installed AND the web interface is accessible AND unauthorized configuration changes can be made by low-privilege users due to missing authorization checks.

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 vendor patch from Cisco for Bug ID CSCuw48188. Until patched, restrict network access to administrative interfaces via firewall rules and monitor for unauthorized configuration changes.

Fix this in Prime Service Catalog Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2015-6395 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2015-6395 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