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

> Physically proximate attackers can view unmasked passwords in the Red Hat QuickStart Cloud Installer web interface, exposing sensitive credentials.

- **Severity:** Medium 4.6 (`CVSS:3.0/AV:P/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:** Yes
- **Published:** 14 Apr 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-w9c7-99vf-c9gw, RHSA-2017:0256

## What is CVE-2016-7060?

CVE-2016-7060 is a medium-severity vulnerability in n/a, published on 14 Apr 2017. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

The web interface in Red Hat QuickStart Cloud Installer (QCI) 1.0 does not mask passwords fields, which allows physically proximate attackers to obtain sensitive password information by reading the display.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `tfm-rubygem-fusor_ui` | Red Hat:qci:1.0::el7 | All versions | 0:1.0.9.1-1.el7sat |
| `tfm-rubygem-fusor_ui-doc` | Red Hat:qci:1.0::el7 | All versions | 0:1.0.9.1-1.el7sat |

Products: Redhat Quickstart Cloud Installer.

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

Apply the vendor's patch.

## Is CVE-2016-7060 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-5411](https://insights.sbomify.com/CVE-2016-5411/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2016-6322](https://insights.sbomify.com/CVE-2016-6322/): Information disclosure in n/a (high 8.4)
- [CVE-2016-6340](https://insights.sbomify.com/CVE-2016-6340/): Weak cryptography in n/a (high 8.4)

## Fix prompt for AI coding agents

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

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

## Sources

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

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