# CVE-2014-4715: Integer overflow in n/a

> Attackers can cause denial of service or potential code execution via crafted input due to integer overflow in LZ4 on 32-bit systems.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jul 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-4715, GHSA-c356-gp5w-pv9x, UBUNTU-CVE-2014-4715

## What is CVE-2014-4715?

CVE-2014-4715 is a medium-severity vulnerability in n/a, published on 3 Jul 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Yann Collet LZ4 before r119, when used on certain 32-bit platforms that allocate memory beyond 0x80000000, does not properly detect integer overflows, which allows context-dependent attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via a crafted Literal Run, a different vulnerability than CVE-2014-4611.

Weakness: CWE-189

## Which versions are affected by CVE-2014-4715?

It affects 1 product.


Products: Yann Collet Lz4.

## How do I fix CVE-2014-4715?

Upgrade to a fixed version.

## Is CVE-2014-4715 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-4715 and fix it if it is affected.

What it is: CVE-2014-4715 is a medium-severity vulnerability in n/a, published on 3 Jul 2014. 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-2014-4715 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-2014-4715/ (Markdown: https://insights.sbomify.com/CVE-2014-4715/index.md)
```

## Sources

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

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