# CVE-2014-3105: Information disclosure in n/a

> Remote attackers can enumerate valid account names in IBM Rational ClearQuest by analyzing distinct error messages returned during failed login attempts.

- **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:** 23 Sep 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-p9xp-4qhh-8rv8

## What is CVE-2014-3105?

CVE-2014-3105 is a medium-severity vulnerability in n/a, published on 23 Sep 2014. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The OSLC integration feature in the Web component in IBM Rational ClearQuest 7.1 before 7.1.2.15, 8.0.0 before 8.0.0.12, and 8.0.1 before 8.0.1.5 provides different error messages for failed login attempts depending on whether the username exists, which allows remote attackers to enumerate account names via a series of requests.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2014-3105?

It affects 1 product.


Products: Ibm Rational Clearcase.

## How do I fix CVE-2014-3105?

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

## Is CVE-2014-3105 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2014-6221](https://insights.sbomify.com/CVE-2014-6221/): Weak cryptography in n/a (critical 9.4)
- [CVE-2014-0931](https://insights.sbomify.com/CVE-2014-0931/): XML external entity in n/a (critical 9.1)
- [CVE-2019-4059](https://insights.sbomify.com/CVE-2019-4059/): Hardcoded credentials in Rational ClearCase (high 7.5)
- [CVE-2015-5039](https://insights.sbomify.com/CVE-2015-5039/): Security feature bypass in n/a (high 7.4)
- [CVE-2013-5415](https://insights.sbomify.com/CVE-2013-5415/): Memory corruption in n/a (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2014-3105 and fix it if it is affected.

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

## Sources

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

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