# CVE-2015-4049: Memory corruption in n/a

> Authenticated users can cause system crashes or data corruption via stack corruption during peak memory usage in Unisys MCP systems.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-7gjq-76c2-rp28

## What is CVE-2015-4049?

CVE-2015-4049 is a medium-severity memory corruption vulnerability in n/a, published on 3 Feb 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Unisys Libra 43xx, 63xx, and 83xx, and FS600 class systems with MCP-FIRMWARE 40.0 before 40.0IC4 Build 270 might allow remote authenticated users to cause a denial of service (data corruption or system crash) via vectors related to using program operators during EPSILON (level 5) based codefiles at peak memory usage, which triggers CPM stack corruption.

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

## Which versions are affected by CVE-2015-4049?

It affects 1 product.


Products: Unisys Mcp-Firmware.

## How do I fix CVE-2015-4049?

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

## Is CVE-2015-4049 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2017-13684](https://insights.sbomify.com/CVE-2017-13684/): Memory corruption in n/a (high 7.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4049 and fix it if it is affected.

What it is: CVE-2015-4049 is a medium-severity memory corruption vulnerability in n/a, published on 3 Feb 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-4049 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-2015-4049/ (Markdown: https://insights.sbomify.com/CVE-2015-4049/index.md)
```

## Sources

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

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