# CVE-2000-1071: Security feature bypass in n/a

> The iCal GUI installer disables X server access control, allowing remote attackers to monitor events and escalate privileges.

- **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:** 22 Jan 2001
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-79g6-x9gh-wwqv

## What is CVE-2000-1071?

CVE-2000-1071 is a critical vulnerability in n/a, published on 22 Jan 2001. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The GUI installation for iCal 2.1 Patch 2 disables access control for the X server using an "xhost +" command, which allows remote attackers to monitor X Windows events and gain privileges.

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

It affects 1 product.


Products: Netscape Iplanet Ical.

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

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

## Is CVE-2000-1071 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-1074](https://insights.sbomify.com/CVE-2000-1074/): Privilege escalation in n/a (critical 10.0)
- [CVE-2000-1072](https://insights.sbomify.com/CVE-2000-1072/): Privilege escalation in n/a (high 7.2)
- [CVE-2000-1073](https://insights.sbomify.com/CVE-2000-1073/): Path traversal in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-1071 is a critical vulnerability in n/a, published on 22 Jan 2001. 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-1071 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-1071/ (Markdown: https://insights.sbomify.com/CVE-2000-1071/index.md)
```

## Sources

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

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