# CVE-2008-1293: Misconfiguration in n/a

> Remote attackers can connect to the X server via TCP port 6006 due to insecure default configuration, bypassing authentication.

- **Severity:** Medium 4.8 (`AV:A/AC:L/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 29 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1293, DSA-1561-1, DTSA-118-1, GHSA-858r-5fj9-h96m

## What is CVE-2008-1293?

CVE-2008-1293 is a medium-severity vulnerability in n/a, published on 29 Apr 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

ldm in Linux Terminal Server Project (LTSP) 0.99 and 2 passes the -ac option to the X server on each LTSP client, which allows remote attackers to connect to this server via TCP port 6006 (aka display :6).

Weakness: CWE-264

## Which versions are affected by CVE-2008-1293?

It affects 1 product.


Products: Ltsp Linux Terminal Server Project.

## How do I fix CVE-2008-1293?

Apply the vendor's patch.

## Is CVE-2008-1293 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-1293 and fix it if it is affected.

What it is: CVE-2008-1293 is a medium-severity vulnerability in n/a, published on 29 Apr 2008. 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-2008-1293 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-2008-1293/ (Markdown: https://insights.sbomify.com/CVE-2008-1293/index.md)
```

## Sources

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

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