# CVE-2000-0429: Hardcoded credentials in n/a

> A hardcoded backdoor password in Cart32 allows remote attackers to execute arbitrary commands without authentication.

- **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:** No
- **Published:** 15 Jun 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-qr5c-3r3w-6h26

## What is CVE-2000-0429?

CVE-2000-0429 is a high-severity vulnerability in n/a, published on 15 Jun 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A backdoor password in Cart32 3.0 and earlier allows remote attackers to execute arbitrary commands.

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

It affects 1 product.


Products: Mcmurtrey Whitaker and Associates Cart32.

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

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

## Is CVE-2000-0429 being exploited?

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

Public exploit code:

- McMurtrey/Whitaker & Associates Cart32 2.6/3.0 - Remote Administration Password (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2000-0136](https://insights.sbomify.com/CVE-2000-0136/): Business logic in n/a (high 7.5)
- [CVE-2004-0675](https://insights.sbomify.com/CVE-2004-0675/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2007-5253](https://insights.sbomify.com/CVE-2007-5253/): Path traversal in n/a (medium 5.0)
- [CVE-2000-0430](https://insights.sbomify.com/CVE-2000-0430/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0429 is a high-severity vulnerability in n/a, published on 15 Jun 2000. 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-2000-0429 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-0429/ (Markdown: https://insights.sbomify.com/CVE-2000-0429/index.md)
```

## Sources

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

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