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

> Remote attackers can execute arbitrary code via a crafted RPM file due to an integer overflow leading to stack-based buffer overflow.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Dec 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-8118, GHSA-wj3v-j872-6xqx, UBUNTU-CVE-2014-8118

## What is CVE-2014-8118?

CVE-2014-8118 is a critical vulnerability in n/a, published on 16 Dec 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Integer overflow in RPM 4.12 and earlier allows remote attackers to execute arbitrary code via a crafted CPIO header in the payload section of an RPM file, which triggers a stack-based buffer overflow.

Weakness: CWE-189

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

It affects 1 product.


Products: Rpm Rpm.

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

Upgrade to a fixed version.

## Is CVE-2014-8118 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-3378](https://insights.sbomify.com/CVE-2011-3378/): Memory corruption in n/a (critical 9.3)
- [CVE-2017-7501](https://insights.sbomify.com/CVE-2017-7501/): Path traversal in rpm (high 7.8)
- [CVE-2017-7500](https://insights.sbomify.com/CVE-2017-7500/): Path traversal in rpm (high 7.3)
- [CVE-2005-4889](https://insights.sbomify.com/CVE-2005-4889/): Race condition in n/a (high 7.2)
- [CVE-2010-2059](https://insights.sbomify.com/CVE-2010-2059/): Race condition in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2014-8118 is a critical vulnerability in n/a, published on 16 Dec 2014. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2014-8118 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-8118/ (Markdown: https://insights.sbomify.com/CVE-2014-8118/index.md)
```

## Sources

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

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