# CVE-2003-0324: Memory corruption in n/a

> Remote malicious IRC servers can trigger buffer overflows in EPIC IRC Client, causing crashes or arbitrary code execution.

- **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:** 22 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0324, DSA-287, GHSA-88jf-xx4f-mf96

## What is CVE-2003-0324?

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

### Official description

Buffer overflows in EPIC IRC Client (EPIC4) 1.0.1 allows remote malicious IRC servers to cause a denial of service (crash) and possibly execute arbitrary code via long replies that are not properly handled by the (1) userhost_cmd_returned function, or (2) Statusbar capability.

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

It affects 1 product.


Products: Epic Epic4.

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

Apply the vendor's patch.

## Is CVE-2003-0324 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0328](https://insights.sbomify.com/CVE-2003-0328/): Integer overflow in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0324 is a high-severity memory corruption vulnerability in n/a, published on 22 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-0324 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-0324/ (Markdown: https://insights.sbomify.com/CVE-2003-0324/index.md)
```

## Sources

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

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