# CVE-2005-0579: Auth bypass in n/a

> Local attackers can bypass X server authentication in FreeNX when the XAUTHORITY variable is unset, gaining unauthorized access to the X session.

- **Severity:** Medium 4.6 (`AV:L/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-qx6r-cp2c-5gr3

## What is CVE-2005-0579?

CVE-2005-0579 is a medium-severity authentication bypass vulnerability in n/a, published on 27 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

nxagent in FreeNX before 0.2.8 does not properly handle when the XAUTHORITY environment variable is not set, which allows local users to access the X server without X authentication.

## Which versions are affected by CVE-2005-0579?

It affects 1 product.


Products: Freenx Freenx.

## How do I fix CVE-2005-0579?

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

## Is CVE-2005-0579 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0579 and fix it if it is affected.

What it is: CVE-2005-0579 is a medium-severity authentication bypass vulnerability in n/a, published on 27 Feb 2005. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-0579 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-2005-0579/ (Markdown: https://insights.sbomify.com/CVE-2005-0579/index.md)
```

## Sources

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

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