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

> Remote attackers can modify domain name information without authentication due to missing password requirements in the administrative interface.

- **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:** 29 Nov 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6hc7-ff75-6g3r

## What is CVE-2000-1023?

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

### Official description

The Alabanza Control Panel does not require passwords to access administrative commands, which allows remote attackers to modify domain name information via the nsManager.cgi CGI program.

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

It affects 1 product.


Products: Alabanza Control Panel.

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

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

## Is CVE-2000-1023 being exploited?

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

Public exploit code:

- Alabanza Control Panel 3.0 - Domain Modification (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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