# CVE-2002-2271: Memory corruption in n/a

> Remote attackers can crash the BigFun IRC client via a buffer overflow in the DCC feature, requiring user interaction to initiate the connection.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:N/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Oct 2007
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-v42q-m8v6-6rj4

## What is CVE-2002-2271?

CVE-2002-2271 is a medium-severity memory corruption vulnerability in n/a, published on 18 Oct 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Buffer overflow in BigFun 1.51b IRC client, when the Direct Client Connection (DCC) option is used, allows remote attackers to cause a denial of service (crash) via a long string.

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

## Which versions are affected by CVE-2002-2271?

It affects 1 product.


Products: Bigfun Bigfun.

## How do I fix CVE-2002-2271?

No fix has been published for CVE-2002-2271 yet. Limit exposure of the affected software until one is available.

## Is CVE-2002-2271 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-2271 and fix it if it is affected.

What it is: CVE-2002-2271 is a medium-severity memory corruption vulnerability in n/a, published on 18 Oct 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2002-2271 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-2002-2271/ (Markdown: https://insights.sbomify.com/CVE-2002-2271/index.md)
```

## Sources

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

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