# CVE-2000-0680: Code injection in n/a

> Remote CVS committers can create malicious Checkin.prog or Update.prog scripts to execute arbitrary code on the server.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-jhvw-wg26-wj9c

## What is CVE-2000-0680?

CVE-2000-0680 is a high-severity code injection vulnerability in n/a, published on 21 Sep 2000. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The CVS 1.10.8 server does not properly restrict users from creating arbitrary Checkin.prog or Update.prog programs, which allows remote CVS committers to modify or create Trojan horse programs with the Checkin.prog or Update.prog names, then performing a CVS commit action.

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

It affects 1 product.


Products: Cvs Cvs.

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

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

## Is CVE-2000-0680 being exploited?

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

Public exploit code:

- CVS Kit CVS Server 1.10.8 - 'Checkin.prog' Binary Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-0804](https://insights.sbomify.com/CVE-2012-0804/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0414](https://insights.sbomify.com/CVE-2004-0414/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0416](https://insights.sbomify.com/CVE-2004-0416/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-0418](https://insights.sbomify.com/CVE-2004-0418/): Memory corruption in n/a (critical 10.0)
- [CVE-2004-1342](https://insights.sbomify.com/CVE-2004-1342/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0680 is a high-severity code injection vulnerability in n/a, published on 21 Sep 2000. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2000-0680 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-0680/ (Markdown: https://insights.sbomify.com/CVE-2000-0680/index.md)
```

## Sources

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

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