# CVE-2000-0757: Auth bypass in n/a

> Remote attackers can gain root privileges by connecting to the unauthenticated sysgen service in Aptis Totalbill.

- **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:** No
- **Published:** 21 Sep 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-xxmv-v72m-r6w4

## What is CVE-2000-0757?

CVE-2000-0757 is a critical authentication bypass vulnerability in n/a, published on 21 Sep 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The sysgen service in Aptis Totalbill does not perform authentication, which allows remote attackers to gain root privileges by connecting to the service and specifying the commands to be executed.

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

It affects 1 product.


Products: Aptis Software Totalbill.

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

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

## Is CVE-2000-0757 being exploited?

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

Public exploit code:

- Aptis Software TotalBill 3.0 - Remote Command Execution (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0757 is a critical authentication bypass vulnerability in n/a, published on 21 Sep 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-0757 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-0757/ (Markdown: https://insights.sbomify.com/CVE-2000-0757/index.md)
```

## Sources

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

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