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

> An integer overflow in pppd allows attackers to corrupt security variables and gain privileged access via a long word in an options file.

- **Severity:** High 7.5 (`AV:N/AC:L/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:** 15 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3158, DLA-74-1, DSA-3079-1, GHSA-4rmp-xhjh-jrfr, MGASA-2014-0368, UBUNTU-CVE-2014-3158, USN-2429-1

## What is CVE-2014-3158?

CVE-2014-3158 is a high-severity vulnerability in n/a, published on 15 Nov 2014. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Integer overflow in the getword function in options.c in pppd in Paul's PPP Package (ppp) before 2.4.7 allows attackers to "access privileged options" via a long word in an options file, which triggers a heap-based buffer overflow that "[corrupts] security-relevant variables."

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

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

It affects 1 product.


Products: Point-to-Point Protocol Project Point-to-Point Protocol.

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

Upgrade to a fixed version.

## Is CVE-2014-3158 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-2194](https://insights.sbomify.com/CVE-2006-2194/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

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

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

## Sources

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

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