# CVE-2016-6034: Information disclosure in Tivoli Storage Manager for Virtual Environments

> High-privilege users can disclose Windows domain credentials in IBM Tivoli Storage Manager for Virtual Environments.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 1 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-cpf3-46qv-gv2r

## What is CVE-2016-6034?

CVE-2016-6034 is a medium-severity vulnerability in IBM Corporation Tivoli Storage Manager for Virtual Environments, published on 1 Feb 2017. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

IBM Tivoli Storage Manager for Virtual Environments (VMware) could disclose the Windows domain credentials to a user with a high level of privileges.

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

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

It affects 1 product.


Products: Ibm Tivoli Storage Manager for Virtual Environments Data Protection for Vmware.

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

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

## Is CVE-2016-6034 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2016-6034 is a medium-severity vulnerability in IBM Corporation Tivoli Storage Manager for Virtual Environments, published on 1 Feb 2017. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-6034 in the wild and no public exploit code.

Affected product: IBM Corporation Tivoli Storage Manager for Virtual Environments. 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-6034/ (Markdown: https://insights.sbomify.com/CVE-2016-6034/index.md)
```

## Sources

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

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