dbcve.org
StealthApplication · Unisys

CVE-2018-6592

HIGH · 7.8 CVSS v3.0 Published 2018-02-19
Fix available
A fix is available. Upgrade to 3.3.016.1 or later.
See remediation →
80/100
Remediation priority · High
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
Unisys Stealth 3.3 Windows endpoints before 3.3.016.1 allow local users to gain access to Stealth-enabled devices by leveraging improper cleanup of memory used for negotiation key storage.

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

Unisys Stealth 3.3 Windows endpoints before version 3.3.016.1 contain a vulnerability where memory used for negotiation key storage is not properly cleaned up. Local users can exploit this improper memory handling to gain unauthorized access to Stealth-enabled devices, representing a local privilege escalation or access control bypass issue.

MitigationUpdate Unisys Stealth Windows endpoints to version 3.3.016.1 or later to address the improper memory cleanup issue.

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
StealthApplication
Affected:>= 3.3, < 3.3.016.1

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

CVSS:3.0/AV:L/AC:L/PR:L/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 if Unisys Stealth is installed
    Check for Unisys Stealth in Windows installed programs (Add/Remove Programs, Programs and Features) or look for Stealth-related processes or services using Task Manager or PowerShell `Get-Process` / `Get-Service`
    Affected if Unisys Stealth software is present on the Windows endpoint
  2. Determine the installed version of Unisys Stealth
    Retrieve the exact version number from the installed program details, using Windows program information (such as `Get-ItemProperty` on the uninstall registry key or the program's About/Properties dialog)
    Affected if The installed version falls within the range >= 3.3 and < 3.3.016.1
  3. Verify the product is active
    Check if Stealth-related services are running on the endpoint, since the vulnerability involves memory handling during operation
    Affected if Stealth services are running on an affected version (versions 3.3 through 3.3.016.0)

A Windows endpoint is affected if Unisys Stealth version 3.3 through 3.3.016.0 is installed and running, as these versions contain the improper memory cleanup flaw that allows local privilege escalation.

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
Upgrade available Upgrade to 3.3.016.1 or later
Fixed in 3.3.016.1
Interim mitigation

Update Unisys Stealth Windows endpoints to version 3.3.016.1 or later to address the improper memory cleanup issue.

Fix this in Stealth 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-6592 — 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-6592 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