# CVE-2008-1692: Security feature bypass in n/a

> Local attackers can hijack X11 connections if Eterm defaults to display :0 without explicit configuration, requiring victim interaction.

- **Severity:** Medium 6.9 (`AV:L/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 7 Apr 2008
- **Updated:** 7 Aug 2024
- **Also known as:** DEBIAN-CVE-2008-1692, GHSA-gg62-cc3q-cr2x

## What is CVE-2008-1692?

CVE-2008-1692 is a medium-severity vulnerability in n/a, published on 7 Apr 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Eterm 0.9.4 opens a terminal window on :0 if -display is not specified and the DISPLAY environment variable is not set, which might allow local users to hijack X11 connections.  NOTE: realistic attack scenarios require that the victim enters a command on the wrong machine.

Weakness: CWE-264

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

It affects 1 product.


Products: Eterm Eterm.

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

Upgrade to a fixed version.

## Is CVE-2008-1692 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2008-1692 is a medium-severity vulnerability in n/a, published on 7 Apr 2008. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2008-1692 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-1692/ (Markdown: https://insights.sbomify.com/CVE-2008-1692/index.md)
```

## Sources

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

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