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

> Remote attackers can enumerate valid usernames in IBM Rational ClearQuest due to inconsistent error messages, facilitating targeted attacks.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Mar 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8m9x-884p-q39p

## What is CVE-2008-1287?

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

### Official description

IBM Rational ClearQuest 7.0.1.1 and 7.0.0.2 generates different error messages depending on whether the username is valid or invalid, which allows remote attackers to enumerate usernames.

Weakness: CWE-16

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

It affects 1 product.


Products: Ibm Rational Clearquest.

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

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

## Is CVE-2008-1287 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4601](https://insights.sbomify.com/CVE-2010-4601/): Other in n/a (critical 10.0)
- [CVE-2012-0708](https://insights.sbomify.com/CVE-2012-0708/): Memory corruption in n/a (critical 9.3)
- [CVE-2011-1390](https://insights.sbomify.com/CVE-2011-1390/): SQL injection in n/a (high 7.5)
- [CVE-2010-2517](https://insights.sbomify.com/CVE-2010-2517/): Multiple unspecified vulnerabilities in IBM Rational ClearQuest before 7.1.1.02 have unknown impact and attack vectors, as demonstrated by an AppScan report. (high 7.5)
- [CVE-2008-5329](https://insights.sbomify.com/CVE-2008-5329/): Missing authorization in n/a (high 7.5)

## Fix prompt for AI coding agents

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

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

## Sources

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

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