# CVE-2016-5927: Information disclosure in n/a

> Local users can discover encrypted passwords by reading application-trace output when specific tracing is enabled in IBM Spectrum Protect.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/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:** 12 Sep 2016
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-hjw4-mmqg-5692

## What is CVE-2016-5927?

CVE-2016-5927 is a medium-severity vulnerability in n/a, published on 12 Sep 2016. 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 Space Management (aka Spectrum Protect for Space Management) 6.3.x before 6.3.2.6, 6.4.x before 6.4.3.3, and 7.1.x before 7.1.6, when certain dsmsetpw tracing is configured, allows local users to discover an encrypted password by reading application-trace output.

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

## Which versions are affected by CVE-2016-5927?

It affects 1 product.


Products: Ibm Tivoli Storage Manager for Space Management.

## How do I fix CVE-2016-5927?

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

## Is CVE-2016-5927 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2012-4859](https://insights.sbomify.com/CVE-2012-4859/): Missing authorization in n/a (high 7.2)
- [CVE-2012-5954](https://insights.sbomify.com/CVE-2012-5954/): Other in n/a (medium 6.4)
- [CVE-2016-5918](https://insights.sbomify.com/CVE-2016-5918/): Information disclosure in Tivoli Storage Manager HSM for Windows (medium 4.7)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-5927 and fix it if it is affected.

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

## Sources

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

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