# CVE-2007-1859: Auth bypass in n/a

> Local users can bypass screen lock authentication in XScreenSaver when remote directory services are used and network connectivity is lost.

- **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:** Yes
- **Published:** 2 May 2007
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2007-1859, GHSA-fr4x-26r9-jx2p, RHSA-2007:0322

## What is CVE-2007-1859?

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

### Official description

XScreenSaver 4.10, when using a remote directory service for credentials, does not properly handle the results from the getpwuid function in drivers/lock.c when there is no network connectivity, which causes XScreenSaver to crash and unlock the screen and allows local users to bypass authentication.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2007-1859?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `xscreensaver` | Red Hat:enterprise_linux:2.1::as | All versions | 1:3.33-4.rhel21.5 |
| `xscreensaver` | Red Hat:enterprise_linux:2.1::aw | All versions | 1:3.33-4.rhel21.5 |
| `xscreensaver` | Red Hat:enterprise_linux:2.1::es | All versions | 1:3.33-4.rhel21.5 |
| `xscreensaver` | Red Hat:enterprise_linux:2.1::ws | All versions | 1:3.33-4.rhel21.5 |
| `xscreensaver` | Red Hat:enterprise_linux:3::as | All versions | 1:4.10-21.el3 |
| `xscreensaver-debuginfo` | Red Hat:enterprise_linux:3::as | All versions | 1:4.10-21.el3 |
| `xscreensaver` | Red Hat:enterprise_linux:3::desktop | All versions | 1:4.10-21.el3 |
| `xscreensaver-debuginfo` | Red Hat:enterprise_linux:3::desktop | All versions | 1:4.10-21.el3 |
| `xscreensaver` | Red Hat:enterprise_linux:3::es | All versions | 1:4.10-21.el3 |
| `xscreensaver-debuginfo` | Red Hat:enterprise_linux:3::es | All versions | 1:4.10-21.el3 |
| `xscreensaver` | Red Hat:enterprise_linux:3::ws | All versions | 1:4.10-21.el3 |
| `xscreensaver-debuginfo` | Red Hat:enterprise_linux:3::ws | All versions | 1:4.10-21.el3 |
| `xscreensaver` | Red Hat:enterprise_linux:4::as | All versions | 1:4.18-5.rhel4.14 |
| `xscreensaver-debuginfo` | Red Hat:enterprise_linux:4::as | All versions | 1:4.18-5.rhel4.14 |
| `xscreensaver` | Red Hat:enterprise_linux:4::desktop | All versions | 1:4.18-5.rhel4.14 |
| `xscreensaver-debuginfo` | Red Hat:enterprise_linux:4::desktop | All versions | 1:4.18-5.rhel4.14 |
| `xscreensaver` | Red Hat:enterprise_linux:4::es | All versions | 1:4.18-5.rhel4.14 |
| `xscreensaver-debuginfo` | Red Hat:enterprise_linux:4::es | All versions | 1:4.18-5.rhel4.14 |
| `xscreensaver` | Red Hat:enterprise_linux:4::ws | All versions | 1:4.18-5.rhel4.14 |
| `xscreensaver-debuginfo` | Red Hat:enterprise_linux:4::ws | All versions | 1:4.18-5.rhel4.14 |

Products: Xscreensaver Xscreensaver.

## How do I fix CVE-2007-1859?

Apply the vendor's patch.

## Is CVE-2007-1859 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2003-0885](https://insights.sbomify.com/CVE-2003-0885/): Path traversal in n/a (medium 6.4)
- [CVE-2004-2655](https://insights.sbomify.com/CVE-2004-2655/): Information disclosure in n/a (medium 5.4)
- [CVE-2007-5585](https://insights.sbomify.com/CVE-2007-5585/): Denial of service in n/a (medium 5.0)
- [CVE-2003-1294](https://insights.sbomify.com/CVE-2003-1294/): Path traversal in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-1859 and fix it if it is affected.

What it is: CVE-2007-1859 is a medium-severity authentication bypass vulnerability in n/a, published on 2 May 2007. 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-2007-1859 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-2007-1859/ (Markdown: https://insights.sbomify.com/CVE-2007-1859/index.md)
```

## Sources

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

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