dbcve.org
Mobility Services EngineApplication · Cisco

CVE-2018-0375

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-18
Fix available
A fix is available. Upgrade to 18.2.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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 the Cluster Manager of Cisco Policy Suite before 18.2.0 could allow an unauthenticated, remote attacker to log in to an affected system using the root account, which has default, static user credentials. The vulnerability is due to the presence of undocumented, static user credentials for the root account. An attacker could exploit this vulnerability by using the account to log in to an affected system. An exploit could allow the attacker to log in to the affected system and execute arbitrary commands as the root user. Cisco Bug IDs: CSCvh02680.

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

A vulnerability in Cisco Policy Suite Cluster Manager before version 18.2.0 allows unauthenticated remote attackers to log in using the root account due to undocumented static credentials hardcoded in the system. This enables arbitrary command execution with root privileges.

MitigationUpgrade to Cisco Policy Suite 18.2.0 or later to replace the vulnerable Cluster Manager, and ensure network access to management interfaces is restricted to authorized personnel only.

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
Mobility Services EngineApplication
Affected:= 14.0.0
Policy SuiteApplication
Affected:< 18.2.0

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

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/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 installed Cisco Policy Suite version
    Run command 'rpm -qa | grep -i policy-suite' or check the Cluster Manager web interface version information page. Alternatively, check /opt/cps/version/info if the installation directory exists.
    Affected if The installed version is less than 18.2.0
  2. Identify installed Cisco Mobility Services Engine version
    Run command 'rpm -qa | grep -i mobility-services-engine' or check the system management interface for the MSE version information.
    Affected if The installed version equals 14.0.0 exactly
  3. Verify Cluster Manager component status
    Check if the Cluster Manager service is running using 'systemctl status cps-cluster-manager' or by accessing the Cluster Manager web portal on the management interface (typically port 8443 or 443).
    Affected if Cluster Manager is running and accessible
  4. Check network exposure of management interfaces
    Review firewall rules and network ACLs to determine if TCP ports used by Cluster Manager (such as 22, 443, 8443) are exposed to untrusted networks. Use 'netstat -tlnp | grep -E "(22|443|8443)"' to list listening management ports.
    Affected if Cluster Manager management ports are reachable from untrusted networks

If either Cisco Policy Suite version is below 18.2.0 or Cisco Mobility Services Engine equals 14.0.0, and the Cluster Manager interface is network-accessible, the environment is affected by CVE-2018-0375.

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.

dbcve · scoped
Upgrade available Upgrade to 18.2.0 or later
Fixed in 18.2.0
Interim mitigation

Upgrade to Cisco Policy Suite 18.2.0 or later to replace the vulnerable Cluster Manager, and ensure network access to management interfaces is restricted to authorized personnel only.

Recommended fix High confidence

Cisco Policy Suite 18.2.0 or later; Mobility Services Engine 14.0.0 to a fixed release (contact Cisco for specific fixed version)

  1. Back up all current configurations and data on the affected Cisco Policy Suite or Mobility Services Engine system
  2. Download Cisco Policy Suite version 18.2.0 or later from the Cisco official download site (requires valid Cisco service contract)
  3. Review Cisco upgrade documentation for Policy Suite before initiating the upgrade process
  4. Execute the upgrade following the documented migration path from your current version
  5. After upgrade, verify that the root account no longer has static/default credentials by checking system documentation or contacting Cisco support
  6. Confirm the vulnerability is resolved by attempting to authenticate with the previously documented default credentials (they should no longer work)
  7. Ensure any external-facing interfaces are properly secured post-upgrade
Caveat Refer to Cisco release notes for version 18.2.0 for any configuration or behavioral changes that may affect existing deployments; always test in non-production environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Mobility Services Engine Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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