# CVE-2005-2772: Memory corruption in n/a

> Remote attackers can execute arbitrary code via stack-based buffer overflows in the Gopher client when processing malicious server replies or launching external programs.

- **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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 2 Sep 2005
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2005-2772, DSA-832-1, GHSA-ww2m-6vp7-cp37

## What is CVE-2005-2772?

CVE-2005-2772 is a high-severity memory corruption vulnerability in n/a, published on 2 Sep 2005. 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

Multiple stack-based buffer overflows in University of Minnesota gopher client 3.0.9 allow remote malicious servers to execute arbitrary code via (1) a long "+VIEWS:" reply, which is not properly handled in the VIfromLine function, and (2) certain arguments when launching third party programs such as a web browser from a web link, which is not properly handled in the FIOgetargv function.

## Which versions are affected by CVE-2005-2772?

It affects 1 product.


Products: University of Minnesota Gopher.

## How do I fix CVE-2005-2772?

Apply the vendor's patch.

## Is CVE-2005-2772 being exploited?

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

Public exploit code:

- Gopher 3.0.9 - '+VIEWS' Client-Side Buffer Overflow (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2005-1853](https://insights.sbomify.com/CVE-2005-1853/): Privilege escalation in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-2772 and fix it if it is affected.

What it is: CVE-2005-2772 is a high-severity memory corruption vulnerability in n/a, published on 2 Sep 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2005-2772 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-2005-2772/ (Markdown: https://insights.sbomify.com/CVE-2005-2772/index.md)
```

## Sources

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

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