# CVE-2000-0244: Weak cryptography in n/a

> Weak XOR encryption in Citrix ICA allows attackers to bypass authentication and potentially take over user accounts.

- **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:** 12 Apr 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-c2cj-5326-gh33

## What is CVE-2000-0244?

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

### Official description

The Citrix ICA (Independent Computing Architecture) protocol uses weak encryption (XOR) for user authentication.

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

It affects 2 products.


Products: Citrix Metaframe, Citrix Winframe.

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

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

## Is CVE-2000-0244 being exploited?

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

Public exploit code:

- Citrix Metaframe 1.0/1.8 - Weak Encryption (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-5821](https://insights.sbomify.com/CVE-2006-5821/): Memory corruption in n/a (high 7.5)
- [CVE-2005-3134](https://insights.sbomify.com/CVE-2005-3134/): Security feature bypass in n/a (high 7.5)
- [CVE-2001-0908](https://insights.sbomify.com/CVE-2001-0908/): Information disclosure in n/a (high 7.5)
- [CVE-2007-0444](https://insights.sbomify.com/CVE-2007-0444/): Memory corruption in n/a (high 7.2)
- [CVE-2006-3779](https://insights.sbomify.com/CVE-2006-3779/): Privilege escalation in n/a (medium 6.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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