# CVE-2018-6592: Information disclosure in n/a

> Local attackers can access Stealth-enabled devices by exploiting improper memory cleanup of negotiation keys in Unisys Stealth Windows endpoints.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-3mf9-3vfv-v8rx

## What is CVE-2018-6592?

CVE-2018-6592 is a high-severity vulnerability in n/a, published on 19 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-404 (Improper Resource Shutdown or Release)

## Which versions are affected by CVE-2018-6592?

It affects 1 product.


Products: Unisys Stealth.

## How do I fix CVE-2018-6592?

No fix has been published for CVE-2018-6592 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-6592 being exploited?

There is no known exploitation of CVE-2018-6592 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2020-12053](https://insights.sbomify.com/CVE-2020-12053/): Auth bypass in n/a (critical 9.8)
- [CVE-2021-3141](https://insights.sbomify.com/CVE-2021-3141/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2020-24620](https://insights.sbomify.com/CVE-2020-24620/): Hardcoded credentials in n/a (high 7.8)
- [CVE-2024-23758](https://insights.sbomify.com/CVE-2024-23758/): Information disclosure in n/a (high 7.5)
- [CVE-2019-18193](https://insights.sbomify.com/CVE-2019-18193/): TODO DODO (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-6592 and fix it if it is affected.

What it is: CVE-2018-6592 is a high-severity vulnerability in n/a, published on 19 Feb 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-6592 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-6592/ (Markdown: https://insights.sbomify.com/CVE-2018-6592/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-6592
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-6592
- OSV: https://osv.dev/vulnerability/CVE-2018-6592

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-6592/
Summaries are generated and may contain mistakes; the official description above is the record.