# CVE-2018-5762: Weak cryptography in n/a

> Remote attackers can decrypt TLS ciphertext data on Unisys ClearPath MCP systems by exploiting a Bleichenbacher RSA padding oracle vulnerability.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-fj56-772w-rr26

## What is CVE-2018-5762?

CVE-2018-5762 is a medium-severity vulnerability in n/a, published on 26 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TLS implementation in the TCP/IP networking module in Unisys ClearPath MCP systems with TCP-IP-SW 58.1 before 58.160, 59.1 before 059.1a.17 (IC #17), and 60.0 before 60.044 might allow remote attackers to decrypt TLS ciphertext data by leveraging a Bleichenbacher RSA padding oracle, aka a ROBOT attack.

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

It affects 1 product.


Products: Unisys Clearpath Mcp.

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

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

## Is CVE-2018-5762 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2002-2179](https://insights.sbomify.com/CVE-2002-2179/): Denial of service in n/a (high 7.8)
- [CVE-2017-5872](https://insights.sbomify.com/CVE-2017-5872/): Denial of service in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-5762 is a medium-severity vulnerability in n/a, published on 26 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-5762 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-5762/ (Markdown: https://insights.sbomify.com/CVE-2018-5762/index.md)
```

## Sources

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

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