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

> Attackers can trigger a buffer overflow in CHICKEN Scheme via crafted substring arguments, potentially leading to code execution or crashes.

- **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:** Not stated
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-9651, GHSA-g3x6-wqp3-hmmm, UBUNTU-CVE-2014-9651

## What is CVE-2014-9651?

CVE-2014-9651 is a high-severity memory corruption vulnerability in n/a, published on 28 Aug 2015. 

### Official description

Buffer overflow in CHICKEN 4.9.0.x before 4.9.0.2, 4.9.x before 4.9.1, and before 5.0 allows attackers to have unspecified impact via a positive START argument to the "substring-index[-ci] procedures."

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

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

It affects 1 product.


Products: Call-Cc Chicken.

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

Upgrade to a fixed version.

## Is CVE-2014-9651 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-45145](https://insights.sbomify.com/CVE-2022-45145/): Command injection in n/a (critical 9.8)
- [CVE-2014-6310](https://insights.sbomify.com/CVE-2014-6310/): Memory corruption in n/a (critical 9.8)
- [CVE-2012-6125](https://insights.sbomify.com/CVE-2012-6125/): Denial of service in chicken (critical 9.8)
- [CVE-2016-6830](https://insights.sbomify.com/CVE-2016-6830/): Memory corruption in n/a (critical 9.8)
- [CVE-2013-2024](https://insights.sbomify.com/CVE-2013-2024/): Command injection in chicken (high 8.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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