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

> Remote attackers can control client X sessions via malicious xauth due to default SSH X forwarding, requiring configuration changes to mitigate.

- **Severity:** Medium 5.1 (`AV:N/AC:H/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6hfg-9p4g-2q8c

## What is CVE-2000-0217?

CVE-2000-0217 is a medium-severity vulnerability in OpenSSH, published on 10 Apr 2000. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The default configuration of SSH allows X forwarding, which could allow a remote attacker to control a client's X sessions via a malicious xauth program.

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

It affects 3 products.


Products: OpenSSH, Ssh Ssh, Ssh Ssh2.

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

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

## Is CVE-2000-0217 being exploited?

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

## Other vulnerabilities in OpenSSH

- [CVE-2003-0786](https://insights.sbomify.com/CVE-2003-0786/): Auth bypass in n/a (critical 10.0)
- [CVE-2003-0693](https://insights.sbomify.com/CVE-2003-0693/): Memory corruption in n/a (critical 10.0)
- [CVE-2002-0640](https://insights.sbomify.com/CVE-2002-0640/): Memory corruption in n/a (critical 10.0)
- [CVE-2001-0144](https://insights.sbomify.com/CVE-2001-0144/): Integer overflow in n/a (critical 10.0)
- [CVE-2000-0999](https://insights.sbomify.com/CVE-2000-0999/): Memory corruption in n/a (critical 10.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0217 is a medium-severity vulnerability in OpenSSH, published on 10 Apr 2000. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2000-0217 in the wild and no public exploit code.

Affected product: OpenSSH. 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-0217/ (Markdown: https://insights.sbomify.com/CVE-2000-0217/index.md)
```

## Sources

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

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