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

> Attackers with physical proximity can read cleartext passwords from trace logs when application tracing is enabled in IBM Tivoli Storage Manager products.

- **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:** Not needed
- **Fix available:** No
- **Published:** 23 Aug 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-2p4q-pg24-pmp6

## What is CVE-2015-6557?

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

### Official description

IBM Tivoli Storage Manager for Databases: Data Protection for Microsoft SQL Server 5.5 before 5.5.6.1, 6.3 before 6.3.1.5, 6.4 before 6.4.1.7, and 7.1 before 7.1.2; Tivoli Storage Manager for Mail: Data Protection for Microsoft Exchange Server 5.5 before 5.5.1.1, 6.1 before 6.1.3.7, 6.3 before 6.3.1.5, 6.4 before 6.4.1.7, and 7.1 before 7.1.2; and Tivoli Storage FlashCopy Manager 3.1 before 3.1.1.5, 3.2 before 3.2.1.7, and 4.1 before 4.1.2, when application tracing is used, place cleartext passwords in exception messages, which allows physically proximate attackers to obtain sensitive information by reading trace output, a different vulnerability than CVE-2015-4949.

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

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

It affects 3 products.


Products: Ibm Tivoli Storage Flashcopy Manager, Ibm Tivoli Storage Manager for Databases Data Protection for Microsoft Sql Server, Ibm Tivoli Storage Manager for Mail Data Protection for Microsoft Exchange Server.

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

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

## Is CVE-2015-6557 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2013-6714](https://insights.sbomify.com/CVE-2013-6714/): Missing authorization in n/a (medium 4.1)
- [CVE-2015-1988](https://insights.sbomify.com/CVE-2015-1988/): Cross-site scripting in n/a (low 3.5)
- [CVE-2015-4949](https://insights.sbomify.com/CVE-2015-4949/): Information disclosure in n/a (low 2.1)
- [CVE-2015-7404](https://insights.sbomify.com/CVE-2015-7404/): Information disclosure in n/a (low 1.9)

## Fix prompt for AI coding agents

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

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

## Sources

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

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