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

> Remote attackers can trigger a buffer overflow in the CHICKEN Scheme library to cause denial of service or execute arbitrary code.

- **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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 20 May 2014
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2014-3776, GHSA-7rfg-5gwp-3v5f

## What is CVE-2014-3776?

CVE-2014-3776 is a high-severity memory corruption vulnerability in n/a, published on 20 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer overflow in the "read-u8vector!" procedure in the srfi-4 unit in CHICKEN stable 4.8.0.7 and development snapshots before 4.9.1 allows remote attackers to cause a denial of service (memory corruption and application crash) and possibly execute arbitrary code via a "#f" value in the NUM argument.

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

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

It affects 1 product.


Products: Call-Cc Chicken.

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

Upgrade to a fixed version.

## Is CVE-2014-3776 being exploited?

There is no known exploitation of CVE-2014-3776 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-3776 and fix it if it is affected.

What it is: CVE-2014-3776 is a high-severity memory corruption vulnerability in n/a, published on 20 May 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2014-3776 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-3776/ (Markdown: https://insights.sbomify.com/CVE-2014-3776/index.md)
```

## Sources

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

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