# CVE-2003-0334: Denial of service in n/a

> Attackers can crash the BitchX IRC client by sending specific channel mode changes, causing a denial of service.

- **Severity:** Low 2.1 (`AV:L/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:** Not needed
- **Fix available:** No
- **Published:** 23 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-32hm-fpxx-4r4p

## What is CVE-2003-0334?

CVE-2003-0334 is a low-severity denial of service vulnerability in n/a, published on 23 May 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

BitchX IRC client 1.0c20cvs and earlier allows attackers to cause a denial of service (core dump) via certain channel mode changes that are not properly handled in names.c.

## Which versions are affected by CVE-2003-0334?

It affects 1 product.


Products: Colten Edwards Bitchx.

## How do I fix CVE-2003-0334?

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

## Is CVE-2003-0334 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2001-0050](https://insights.sbomify.com/CVE-2001-0050/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0321](https://insights.sbomify.com/CVE-2003-0321/): Memory corruption in n/a (high 7.5)
- [CVE-2003-0322](https://insights.sbomify.com/CVE-2003-0322/): Integer overflow in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0334 and fix it if it is affected.

What it is: CVE-2003-0334 is a low-severity denial of service vulnerability in n/a, published on 23 May 2003. 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-2003-0334 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-2003-0334/ (Markdown: https://insights.sbomify.com/CVE-2003-0334/index.md)
```

## Sources

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

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