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

> Attackers can read sensitive credentials from logs in RabbitMQ for PCF due to improper logging of failed command lines.

- **Severity:** High 7.5 (`CVSS:3.0/AV:N/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:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Sep 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-65f6-2v57-3w6h

## What is CVE-2016-0929?

CVE-2016-0929 is a high-severity vulnerability in n/a, published on 18 Sep 2016. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The metrics-collection component in RabbitMQ for Pivotal Cloud Foundry (PCF) 1.6.x before 1.6.4 logs command lines of failed commands, which might allow context-dependent attackers to obtain sensitive information by reading the log data, as demonstrated by a syslog message that contains credentials from a command line.

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

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

It affects 1 product.


Products: Pivotal Software Rabbitmq.

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

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

## Is CVE-2016-0929 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1279](https://insights.sbomify.com/CVE-2018-1279/): RabbitMQ cluster compromise due to deterministically generated cookie (high 8.5)
- [CVE-2014-9494](https://insights.sbomify.com/CVE-2014-9494/): RabbitMQ before 3.4.0 allows remote attackers to bypass the loopback_users restriction via a crafted X-Forwareded-For header. (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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