# CVE-2015-5045: Information disclosure in n/a

> Local users can obtain sensitive information from the IBM Rational License Key Server administration tool.

- **Severity:** Low 3.3 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Mar 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-ppj2-439w-8fvg

## What is CVE-2015-5045?

CVE-2015-5045 is a low-severity vulnerability in n/a, published on 26 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The Administration and Reporting tool in IBM Rational License Key Server (RLKS) before 8.1.4.9 iFix 04 allows local users to obtain sensitive information via unspecified vectors. IBM X-Force ID: 106938.

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

## Which versions are affected by CVE-2015-5045?

It affects 1 product.


Products: Ibm Rational License Key Server.

## How do I fix CVE-2015-5045?

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

## Is CVE-2015-5045 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2011-1389](https://insights.sbomify.com/CVE-2011-1389/): Path traversal in n/a (critical 10.0)
- [CVE-2014-0909](https://insights.sbomify.com/CVE-2014-0909/): Information disclosure in n/a (medium 5.0)
- [CVE-2015-1907](https://insights.sbomify.com/CVE-2015-1907/): Information disclosure in n/a (medium 4.0)
- [CVE-2014-4756](https://insights.sbomify.com/CVE-2014-4756/): Auth bypass in n/a (low 3.5)
- [CVE-2014-3079](https://insights.sbomify.com/CVE-2014-3079/): Missing authorization in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-5045 and fix it if it is affected.

What it is: CVE-2015-5045 is a low-severity vulnerability in n/a, published on 26 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2015-5045 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-2015-5045/ (Markdown: https://insights.sbomify.com/CVE-2015-5045/index.md)
```

## Sources

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

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