dbcve.org
Mobility Services EngineApplication · Cisco

CVE-2018-0377

CRITICAL · 9.8 CVSS v3.0 Published 2018-07-18
Fix available
A fix is available. Upgrade to 18.1.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 Open Systems Gateway initiative (OSGi) interface of Cisco Policy Suite before 18.1.0 could allow an unauthenticated, remote attacker to directly connect to the OSGi interface. The vulnerability is due to a lack of authentication. An attacker could exploit this vulnerability by directly connecting to the OSGi interface. An exploit could allow the attacker to access or change any files that are accessible by the OSGi process. Cisco Bug IDs: CSCvh18017.

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 critical authentication bypass vulnerability exists in the OSGi (Open Systems Gateway initiative) interface of Cisco Policy Suite versions prior to 18.1.0. The interface lacks any authentication mechanism, allowing unauthenticated remote attackers to directly connect and access or modify any files accessible to the OSGi process. This gives attackers equivalent file system access to the OSGi service account.

MitigationUpgrade to Cisco Policy Suite version 18.1.0 or later. If immediate upgrade is not feasible, implement network-level access controls to restrict or block unauthorized access to the OSGi interface port.

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.1.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 Cisco Policy Suite installation
    Search for Cisco Policy Suite processes or installation directories - check /opt/cps/ or look for running 'cps' processes using ps aux | grep cps
    Affected if Cisco Policy Suite software is present on the system
  2. Determine installed Cisco Policy Suite version
    Run version detection command: rpm -qa | grep cps or check /opt/cps/version if the directory exists
    Affected if Installed version is below 18.1.0
  3. Identify Cisco Mobility Services Engine installation
    Check for Cisco Mobility Services Engine processes or installation at /opt/mse/ or look for 'mse' processes
    Affected if Cisco Mobility Services Engine version 14.0.0 is running
  4. Detect OSGi interface port exposure
    Check for open OSGi ports (commonly 8081) using netstat -an | grep 8081 or ss -tlnp | grep 8081
    Affected if OSGi port is listening and exposed to network
  5. Verify OSGi interface lacks authentication
    Attempt unauthenticated HTTP request to OSGi endpoint, e.g., curl http://localhost:8081/ or curl http://target:8081/ - if response returns without requiring login credentials
    Affected if OSGi interface accepts requests without any authentication

System is affected if either Cisco Policy Suite below version 18.1.0 or Cisco Mobility Services Engine version 14.0.0 is running and the OSGi interface is accessible without authentication.

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.1.0 or later
Fixed in 18.1.0
Interim mitigation

Upgrade to Cisco Policy Suite version 18.1.0 or later. If immediate upgrade is not feasible, implement network-level access controls to restrict or block unauthorized access to the OSGi interface port.

Recommended fix High confidence

Cisco Policy Suite 18.1.0 or later (Mobility Services Engine: contact Cisco for specific fixed version)

  1. Identify the current version of Cisco Policy Suite running in the environment
  2. If the current version is before 18.1.0, plan for an upgrade to version 18.1.0 or later
  3. Schedule a maintenance window for the upgrade
  4. Back up current configuration data before performing the upgrade
  5. Upgrade Cisco Policy Suite to version 18.1.0 or the latest stable release
  6. After upgrade, verify the OSGi interface now requires authentication
  7. Confirm that the system is functioning correctly post-upgrade
  8. For Mobility Services Engine version 14.0.0, contact Cisco support to confirm if a separate patch or update is required

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

Fix this in Mobility Services Engine 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 the upgrade done

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-0377 — 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-0377 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