dbcve.org
Prime Service CatalogApplication · Cisco

CVE-2018-0285

MEDIUM · 6.5 CVSS v3.0 Published 2018-05-02
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
A vulnerability in service logging for Cisco Prime Service Catalog could allow an authenticated, remote attacker to deny service to the user interface. The vulnerability is due to exhaustion of disk space. An attacker could exploit this vulnerability by performing certain operations that lead to excessive logging. A successful exploit could allow the attacker to deny service to the user interface. Cisco Bug IDs: CSCvd39568.

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 has a denial-of-service vulnerability where an authenticated remote attacker can cause excessive logging that exhausts disk space, rendering the user interface unavailable. The vulnerability stems from unbounded logging of certain operations.

MitigationImplement log rotation policies with size limits and retention periods, configure disk space monitoring with alerts, and consider rate-limiting or filtering excessive logging operations.

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:= 11.1.2

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Verify Cisco Prime Service Catalog installation
    Locate the installation directory - typically under /opt/cisco/ or C:\Program Files\Cisco\ on the server. Check for the 'xportal' or 'primeservice' directories and the main application executables (xplatform.exe or equivalent).
    Affected if The product is not installed in expected locations.
  2. Identify installed version
    Check the version file or about page in the web interface. Common locations: <install_dir>/version.txt, or access https://<server>/primeapp/about.jsp, or check the Windows installer properties.
    Affected if The installed version is exactly 11.1.2.
  3. Confirm web interface is accessible
    Attempt to access the Cisco Prime Service Catalog web portal at the standard URL (typically /root/ or /primeapp/). Verify the login page loads.
    Affected if The web interface is unreachable or returns errors.
  4. Check disk space on log volumes
    Run 'df -h' (Linux) or check disk properties in Windows for the drive containing the installation. Review log directory sizes.
    Affected if Disk space on log volumes is critically low (below 10% free) with unusually large log files.
  5. Inspect log files for excessive entries
    Navigate to the logs directory (typically <install_dir>/xportal/logs/ or <install_dir>/primeservice/logs/). Check for rapidly growing log files with timestamps showing recent activity.
    Affected if Log files are growing abnormally large or contain repeated entries indicating unbounded logging of specific operations.

The environment is affected if Cisco Prime Service Catalog version 11.1.2 is installed with its web interface accessible and showing signs of disk exhaustion from excessive logging.

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

Implement log rotation policies with size limits and retention periods, configure disk space monitoring with alerts, and consider rate-limiting or filtering excessive logging operations.

Fix this in Prime Service Catalog Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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