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

> A stack-based buffer overflow in cifs-utils allows remote attackers to cause unspecified impacts, potentially leading to code execution or denial of service.

- **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 stated
- **Attackable:** Not stated
- **Victim action needed:** Not stated
- **Fix available:** Yes
- **Published:** 31 Mar 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-2830, ECHO-9cf0-966b-4f31, GHSA-88m7-qhcf-97c3, MGASA-2014-0242

## What is CVE-2014-2830?

CVE-2014-2830 is a critical memory corruption vulnerability in n/a, published on 31 Mar 2015. 

### Official description

Stack-based buffer overflow in cifskey.c or cifscreds.c in cifs-utils before 6.4, as used in pam_cifscreds, allows remote attackers to have unspecified impact via unknown vectors.

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

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

It affects 1 product.


Products: Debian Cifs-Utils.

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

Upgrade to a fixed version.

## Is CVE-2014-2830 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-1586](https://insights.sbomify.com/CVE-2012-1586/): Information disclosure in n/a (low 2.1)

## Fix prompt for AI coding agents

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

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

## Sources

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

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