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

> Attackers can execute arbitrary code on UMN gopher servers via buffer overflows in LIST commands or view-type calculations.

- **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:** 19 Sep 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2003-0805, DSA-387, GHSA-5qmr-w3f3-wh84

## What is CVE-2003-0805?

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

### Official description

Multiple buffer overflows in UMN gopher daemon (gopherd) 2.x and 3.x before 3.0.6 allows attackers to execute arbitrary code via (1) a long filename as a result of a LIST command, and (2) the GSisText function, which calculates the view-type.

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

It affects 1 product.


Products: University of Minnesota Gopherd.

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

Upgrade to a fixed version.

## Is CVE-2003-0805 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0805 exists.

Public exploit code:

- University of Minnesota Gopherd 2.0.x/2.3/3.0.x - FTP Gateway Buffer Overflow (exploitdb)
- University of Minnesota Gopherd 2.0.x/2.3/3.0.x - GSisText Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0743](https://insights.sbomify.com/CVE-2000-0743/): Memory corruption in n/a (critical 10.0)
- [CVE-1999-0124](https://insights.sbomify.com/CVE-1999-0124/): Path traversal in n/a (critical 10.0)
- [CVE-2004-0560](https://insights.sbomify.com/CVE-2004-0560/): Integer overflow in n/a (high 7.5)
- [CVE-2004-0561](https://insights.sbomify.com/CVE-2004-0561/): Other in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0805 is a high-severity memory corruption vulnerability in n/a, published on 19 Sep 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2003-0805 exists.

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-0805/ (Markdown: https://insights.sbomify.com/CVE-2003-0805/index.md)
```

## Sources

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

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