# CVE-2008-0663: Information disclosure in n/a

> An attacker with physical access to a locked Novell Client system can read clipboard contents by pasting them into the Challenge Question field.

- **Severity:** Low 2.1 (`AV:L/AC:L/Au:N/C:P/I:N/A:N`)
- **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:** No
- **Published:** 8 Feb 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-78gp-485q-x3wf

## What is CVE-2008-0663?

CVE-2008-0663 is a low-severity vulnerability in n/a, published on 8 Feb 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

Novell Challenge Response Client (LCM) 2.7.5 and earlier, as used with Novell Client for Windows 4.91 SP4, allows users with physical access to a locked system to obtain contents of the clipboard by pasting the contents into the Challenge Question field.

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

It affects 2 products.


Products: Novell Challenge Response Client, Novell Novell Client for Windows.

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

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

## Is CVE-2008-0663 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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