# CVE-2017-13684: Memory corruption in n/a

> Remote authenticated users can cause denial of service or other impacts via stack corruption in Unisys Libra systems.

- **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:** 29 Sep 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-7429-3j4f-m57h

## What is CVE-2017-13684?

CVE-2017-13684 is a high-severity memory corruption vulnerability in n/a, published on 29 Sep 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Unisys Libra 64xx and 84xx and FS601 class systems with MCP-FIRMWARE before 43.211 allow remote authenticated users to cause a denial of service (program crash) or have unspecified other impact via vectors related to incorrect literal handling, which trigger CPM stack corruption.

Weakness: CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer)

## Which versions are affected by CVE-2017-13684?

It affects 1 product.


Products: Unisys Mcp-Firmware.

## How do I fix CVE-2017-13684?

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

## Is CVE-2017-13684 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-4049](https://insights.sbomify.com/CVE-2015-4049/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-13684 and fix it if it is affected.

What it is: CVE-2017-13684 is a high-severity memory corruption vulnerability in n/a, published on 29 Sep 2017. 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-2017-13684 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-2017-13684/ (Markdown: https://insights.sbomify.com/CVE-2017-13684/index.md)
```

## Sources

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

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