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

> Attackers can obtain sensitive user credentials because Cloud Foundry logs user-provided service objects during creation.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 May 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-6q7m-3j88-7g48

## What is CVE-2016-5006?

CVE-2016-5006 is a critical vulnerability in n/a, published on 2 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Cloud Controller in Cloud Foundry before 239 logs user-provided service objects at creation, which allows attackers to obtain sensitive user credential information via unspecified vectors.

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

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

It affects 2 products.


Products: Pivotal Software Cloud Foundry, Pivotal Software Cloud Foundry Elastic Runtime.

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

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

## Is CVE-2016-5006 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2016-5016](https://insights.sbomify.com/CVE-2016-5016/): Cloud Foundry vulnerable to Improper Certificate Validation (medium 5.9)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-5006 is a critical vulnerability in n/a, published on 2 May 2017. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2016-5006 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-5006/ (Markdown: https://insights.sbomify.com/CVE-2016-5006/index.md)
```

## Sources

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

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