# CVE-2014-7912: Memory corruption in n/a

> Remote attackers can execute arbitrary code or cause denial of service via malicious DHCP messages due to improper validation in the dhcpcd client.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Jul 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-7912, GHSA-f6q4-hgr5-frj4, UBUNTU-CVE-2014-7912

## What is CVE-2014-7912?

CVE-2014-7912 is a medium-severity memory corruption vulnerability in n/a, published on 30 Jul 2015. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The get_option function in dhcp.c in dhcpcd before 6.2.0, as used in dhcpcd 5.x in Android before 5.1 and other products, does not validate the relationship between length fields and the amount of data, which allows remote DHCP servers to execute arbitrary code or cause a denial of service (memory corruption) via a large length value of an option in a DHCPACK message.

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

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

It affects 1 product.


Products: Dhcpcd Project Dhcpcd.

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

Upgrade to a fixed version.

## Is CVE-2014-7912 being exploited?

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

Public exploit code:

- exp for cve-2014-7911 which can get system privillage (github_poc): https://github.com/vaginessa/cve-2014-7912

## Other vulnerabilities in n/a

- [CVE-2019-11577](https://insights.sbomify.com/CVE-2019-11577/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-1503](https://insights.sbomify.com/CVE-2016-1503/): Memory corruption in n/a (critical 9.8)
- [CVE-2016-1504](https://insights.sbomify.com/CVE-2016-1504/): dhcpcd before 6.10.0 allows remote attackers to cause a denial of service (invalid read and crash) via vectors related to the option length. (high 7.5)
- [CVE-2026-56116](https://insights.sbomify.com/CVE-2026-56116/): dhcpcd Memory Leak DoS via IPv6 Router Advertisement Handling (high 7.1)
- [CVE-2014-7913](https://insights.sbomify.com/CVE-2014-7913/): Memory corruption in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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