dbcve.org
Prime Service CatalogApplication · Cisco

CVE-2018-0107

HIGH · 8.8 CVSS v3.0 Published 2018-01-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 web framework of Cisco Prime Service Catalog could allow an unauthenticated, remote attacker to execute unwanted actions on an affected device. The vulnerability is due to a lack of cross-site request forgery (CSRF) protection. An attacker could exploit this vulnerability by tricking the user of a web application into executing an adverse action. Cisco Bug IDs: CSCvg30313.

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 confidence

A cross-site request forgery (CSRF) vulnerability in Cisco Prime Service Catalog's web framework allows unauthenticated remote attackers to execute unwanted actions by tricking authenticated users into clicking malicious links or visiting crafted web pages, due to missing anti-CSRF tokens and origin validation.

MitigationEnable CSRF protection by implementing anti-CSRF tokens on all state-changing operations (forms, API endpoints) and validating Origin/Referer headers to ensure requests originate from trusted sources.

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:all versions

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
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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
    Locate the installed version through the product's web interface (typically under Help > About) or by checking the installation directory for version files
    Affected if The installed version is any version of Cisco Prime Service Catalog (all versions are affected per CVE-2018-0107)
  2. Inspect web forms for CSRF token presence
    Use a browser developer tool or HTTP proxy to capture a request when submitting a state-changing form (such as user creation, configuration change, or data submission). Examine if the form includes a hidden anti-CSRF token field
    Affected if Forms lack hidden anti-CSRF token fields - the request contains only basic form data without a token parameter
  3. Verify Origin header validation
    Send an HTTP request to the application from an untrusted origin (simulate a cross-origin request using curl or similar tool) and observe whether the application rejects the request based on Origin header validation
    Affected if The application accepts requests from arbitrary origins without validation - no error or rejection occurs for unexpected Origin values
  4. Check Referer header validation
    Submit a request with a missing or forged Referer header (using a tool to modify HTTP headers) and determine if the application validates that the Referer matches trusted sources
    Affected if The application processes requests regardless of Referer header value - no validation rejects requests with missing or unexpected Referer headers
  5. Review web framework security configuration
    Examine the application's configuration files or admin panel settings for CSRF protection mechanisms - look for options labeled as anti-CSRF, token validation, or request origin validation
    Affected if CSRF protection settings are disabled, not configured, or missing entirely from the web framework configuration

A user is affected if they have Cisco Prime Service Catalog installed and the application lacks anti-CSRF tokens in forms and/or does not validate Origin/Referer headers.

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

Enable CSRF protection by implementing anti-CSRF tokens on all state-changing operations (forms, API endpoints) and validating Origin/Referer headers to ensure requests originate from trusted sources.

Fix this in Prime Service Catalog Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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