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

> Attackers can cause a denial of service via out-of-bounds read in SAP MaxDB and related components' LZH decompression implementation.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 2 Jun 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w343-46q8-7x26

## What is CVE-2015-2278?

CVE-2015-2278 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jun 2015. 

### Official description

The LZH decompression implementation (CsObjectInt::BuildHufTree function in vpa108csulzh.cpp) in SAP MaxDB 7.5 and 7.6, Netweaver Application Server ABAP, Netweaver Application Server Java, Netweaver RFC SDK, GUI, RFC SDK, SAPCAR archive tool, and other products allows context-dependent attackers to cause a denial of service (out-of-bounds read) via unspecified vectors, related to look-ups of non-simple codes, aka SAP Security Note 2124806, 2121661, 2127995, and 2125316.

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

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

It affects 6 products.


Products: Sap Gui, Sap Maxdb, Sap Netweaver Abap Application Server, Sap Netweaver Java Application Server, Sap Netweaver Rfc Sdk, Sap Rfc Library.

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

Apply the vendor's patch.

## Is CVE-2015-2278 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2015-2282](https://insights.sbomify.com/CVE-2015-2282/): Memory corruption in n/a (high 7.5)
- [CVE-2022-41205](https://insights.sbomify.com/CVE-2022-41205/): Code injection in SAP GUI for Windows (medium 5.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2015-2278 is a medium-severity memory corruption vulnerability in n/a, published on 2 Jun 2015. 
Exploitation: There is no known exploitation of CVE-2015-2278 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-2278/ (Markdown: https://insights.sbomify.com/CVE-2015-2278/index.md)
```

## Sources

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

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