# CVE-2000-0035: Command injection in n/a

> Local attackers can execute arbitrary commands and gain privileges via shell metacharacters in the Majordomo resend command.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Feb 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4wrx-2682-w227

## What is CVE-2000-0035?

CVE-2000-0035 is a medium-severity command injection vulnerability in n/a, published on 4 Feb 2000. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

resend command in Majordomo allows local users to gain privileges via shell metacharacters.

## Which versions are affected by CVE-2000-0035?

It affects 1 product.


Products: Great Circle Associates Majordomo.

## How do I fix CVE-2000-0035?

No fix has been published for CVE-2000-0035 yet. Limit exposure of the affected software until one is available.

## Is CVE-2000-0035 being exploited?

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

Public exploit code:

- Great Circle Associates Majordomo 1.94.4 - Local resend (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2003-1367](https://insights.sbomify.com/CVE-2003-1367/): Information disclosure in n/a (high 7.8)
- [CVE-1999-1220](https://insights.sbomify.com/CVE-1999-1220/): Command injection in n/a (high 7.5)
- [CVE-1999-0207](https://insights.sbomify.com/CVE-1999-0207/): Command injection in n/a (high 7.5)
- [CVE-2000-0037](https://insights.sbomify.com/CVE-2000-0037/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0035 and fix it if it is affected.

What it is: CVE-2000-0035 is a medium-severity command injection vulnerability in n/a, published on 4 Feb 2000. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0035 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-2000-0035/ (Markdown: https://insights.sbomify.com/CVE-2000-0035/index.md)
```

## Sources

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

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