Mcp FirmwareOperating system · Unisys

CVE-2019-18386

HIGH · 8.7 CVSS v3.1 Published 2020-01-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
96/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
Systems management on Unisys ClearPath Forward Libra and ClearPath MCP Software Series can fault and have other unspecified impact when receiving specifically crafted message payloads over a systems management communication channel

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 vulnerability exists in the systems management component of Unisys ClearPath Forward Libra and ClearPath MCP Software Series. An attacker can send specifically crafted message payloads over the systems management communication channel to cause the system to fault, potentially leading to denial of service or other unspecified impact. The vulnerability is exploitable remotely with low complexity.

MitigationApply vendor-supplied patches for ClearPath MCP systems management. If patches are unavailable, restrict network access to systems management communication channels and monitor for anomalous message traffic.

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
Mcp FirmwareOperating system
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
High
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:N/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. Confirm Unisys ClearPath MCP system presence
    Identify if the target environment contains Unisys ClearPath Forward Libra or ClearPath MCP systems. Check system inventory, hardware labels, or running system identification commands provided by Unisys for your environment.
    Affected if The system is a Unisys ClearPath Forward Libra or ClearPath MCP system running any firmware version.
  2. Verify systems management component is enabled
    Locate and inspect the systems management communication channel configuration. Consult Unisys documentation for your specific version to identify the management interface configuration file or command that controls the systems management component.
    Affected if The systems management component is active and accessible on the system.
  3. Determine firmware version
    Execute the Unisys-provided command or procedure to query the current Mcp Firmware version installed on the system. This is typically done through the system management interface or console.
    Affected if The installed Mcp Firmware version falls within any version range, since all versions are affected.
  4. Assess network exposure of management interface
    Review network configuration, firewall rules, and access controls surrounding the systems management communication channel. Determine if the management interface is reachable from network segments accessible to untrusted users.
    Affected if The systems management interface is exposed to untrusted or public network segments without adequate access controls.

The environment is affected if it contains any Unisys ClearPath Forward Libra or ClearPath MCP system where the systems management component is enabled and accessible, regardless of firmware version since all versions are vulnerable.

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 vendor-supplied patches for ClearPath MCP systems management. If patches are unavailable, restrict network access to systems management communication channels and monitor for anomalous message traffic.

Fix this in Mcp Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA4.0 h
40.0 hours of engineering $7,000
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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