# CVE-2000-0113: Missing authorization in n/a

> Remote attackers can access network statistics or cause denial of service due to improper access restrictions on the SyGate administration service.

- **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:** 2 Jun 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cj7c-7233-qrq9

## What is CVE-2000-0113?

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

### Official description

The SyGate Remote Management program does not properly restrict access to its administration service, which allows remote attackers to cause a denial of service, or access network traffic statistics.

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

It affects 1 product.


Products: Sybergen Sygate.

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

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

## Is CVE-2000-0113 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0569](https://insights.sbomify.com/CVE-2000-0569/): Denial of service in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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