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

> Attackers can cause denial of service or execute arbitrary code via buffer overflows in the ecartis mailing list server.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 25 Mar 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-34m5-cpcv-cf78

## What is CVE-2003-0782?

CVE-2003-0782 is a critical memory corruption vulnerability in n/a, published on 25 Mar 2004. It can be exploited over the network, with no action from the victim.

### Official description

Multiple buffer overflows in ecartis before 1.0.0 allow attackers to cause a denial of service and possibly execute arbitrary code.

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

It affects 1 product.


Products: Ecartis Ecartis.

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

Upgrade to a fixed version.

## Is CVE-2003-0782 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0781](https://insights.sbomify.com/CVE-2003-0781/): Information disclosure in n/a (critical 10.0)
- [CVE-2002-0467](https://insights.sbomify.com/CVE-2002-0467/): Memory corruption in n/a (critical 10.0)
- [CVE-2003-0162](https://insights.sbomify.com/CVE-2003-0162/): Business logic in n/a (high 7.5)
- [CVE-2002-0469](https://insights.sbomify.com/CVE-2002-0469/): Privilege escalation in n/a (high 7.2)
- [CVE-2006-0332](https://insights.sbomify.com/CVE-2006-0332/): File upload in n/a (medium 6.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0782 is a critical memory corruption vulnerability in n/a, published on 25 Mar 2004. It can be exploited over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0782 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-0782/ (Markdown: https://insights.sbomify.com/CVE-2003-0782/index.md)
```

## Sources

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

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