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

> Remote attackers can discover cleartext passwords in IBM Security Identity Manager via a crafted request, exposing sensitive credentials.

- **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:** 18 Nov 2014
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cpf9-3r7h-48qv

## What is CVE-2014-6098?

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

### Official description

IBM Security Identity Manager 6.x before 6.0.0.3 IF14 allows remote attackers to discover cleartext passwords via a crafted request.

Weakness: CWE-255

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

It affects 1 product.


Products: Ibm Security Identity Manager.

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

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

## Is CVE-2014-6098 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1969](https://insights.sbomify.com/CVE-2018-1969/): File upload in Security Identity Manager (critical 9.0)
- [CVE-2018-1453](https://insights.sbomify.com/CVE-2018-1453/): File upload in Security Identity Manager (high 8.8)
- [CVE-2016-0335](https://insights.sbomify.com/CVE-2016-0335/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2014-6106](https://insights.sbomify.com/CVE-2014-6106/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2019-4561](https://insights.sbomify.com/CVE-2019-4561/): Deserialization in Security Identity Manager (high 8.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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