# CVE-2012-0806: Memory corruption in n/a

> Remote authenticated users can execute arbitrary code via a buffer overflow in the Bip IRC proxy triggered by multiple TCP connections.

- **Severity:** Medium 6.5 (`AV:N/AC:L/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Jan 2012
- **Updated:** 6 Aug 2024
- **Also known as:** DEBIAN-CVE-2012-0806, DSA-2393-1, GHSA-pw5x-fxvq-fjq4

## What is CVE-2012-0806?

CVE-2012-0806 is a medium-severity memory corruption vulnerability in n/a, published on 27 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Buffer overflow in Bip 0.8.8 and earlier might allow remote authenticated users to execute arbitrary code via vectors involving a series of TCP connections that triggers use of many open file descriptors.

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

## Which versions are affected by CVE-2012-0806?

It affects 1 product.


Products: Duckcorp Bip.

## How do I fix CVE-2012-0806?

Apply the vendor's patch.

## Is CVE-2012-0806 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-4550](https://insights.sbomify.com/CVE-2013-4550/): Other in n/a (medium 5.1)
- [CVE-2010-3071](https://insights.sbomify.com/CVE-2010-3071/): Null dereference in n/a (medium 5.0)
- [CVE-2011-5268](https://insights.sbomify.com/CVE-2011-5268/): Denial of service in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-0806 and fix it if it is affected.

What it is: CVE-2012-0806 is a medium-severity memory corruption vulnerability in n/a, published on 27 Jan 2012. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2012-0806 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-2012-0806/ (Markdown: https://insights.sbomify.com/CVE-2012-0806/index.md)
```

## Sources

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

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