# CVE-2002-0901: Memory corruption in n/a

> Remote attackers can execute arbitrary code via buffer overflows in the amindexd daemon, while local users can exploit similar flaws in various command-line tools.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 31 Aug 2002
- **Updated:** 8 Aug 2024
- **Also known as:** DEBIAN-CVE-2002-0901, GHSA-4ff8-c98x-v6m4

## What is CVE-2002-0901?

CVE-2002-0901 is a critical memory corruption vulnerability in n/a, published on 31 Aug 2002. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple buffer overflows in Advanced Maryland Automatic Network Disk Archiver (AMANDA) 2.3.0.4 allow (1) remote attackers to execute arbitrary code via long commands to the amindexd daemon, or certain local users to execute arbitrary code via long command line arguments to the programs (2) amcheck, (3) amgetidx, (4) amtrmidx, (5) createindex-dump, or (6) createindex-gnutar.

## Which versions are affected by CVE-2002-0901?

It affects 1 product.


Products: Amanda Amanda.

## How do I fix CVE-2002-0901?

Upgrade to a fixed version.

## Is CVE-2002-0901 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-37703](https://insights.sbomify.com/CVE-2022-37703/): Path traversal in n/a (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0901 and fix it if it is affected.

What it is: CVE-2002-0901 is a critical memory corruption vulnerability in n/a, published on 31 Aug 2002. 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-2002-0901 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-2002-0901/ (Markdown: https://insights.sbomify.com/CVE-2002-0901/index.md)
```

## Sources

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

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