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

> Local users can read cleartext SQL Server passwords from the MMC GUI Task List, exposing sensitive database credentials.

- **Severity:** Medium 6.2 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:N/S:U/C:H/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:** 8 Aug 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-4hqw-7ch5-h84q

## What is CVE-2016-3059?

CVE-2016-3059 is a medium-severity vulnerability in n/a, published on 8 Aug 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 Databases: Data Protection for Microsoft SQL Server (aka IBM Spectrum Protect for Databases) 6.3 before 6.3.1.7 and 6.4 before 6.4.1.9 and Tivoli Storage FlashCopy Manager for Microsoft SQL Server (aka IBM Spectrum Protect Snapshot) 3.1 before 3.1.1.7 and 3.2 before 3.2.1.9 allow local users to discover a cleartext SQL Server password by reading the Task List in the MMC GUI.

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

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

It affects 2 products.


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

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

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

## Is CVE-2016-3059 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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