# CVE-2018-1000060: Information disclosure in n/a

> Attackers with log access can view sensitive configuration data like passwords due to improper redaction in Sensu Core.

- **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:** Yes
- **Published:** 9 Feb 2018
- **Updated:** 5 Aug 2024
- **Also known as:** RHSA-2018:0616, RHSA-2018:1112, RHSA-2018:1606

## What is CVE-2018-1000060?

CVE-2018-1000060 is a critical vulnerability in n/a, published on 9 Feb 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Sensu, Inc. Sensu Core version Before 1.2.0 & before commit 46ff10023e8cbf1b6978838f47c51b20b98fe30b contains a CWE-522 vulnerability in Sensu::Utilities.redact_sensitive() that can result in sensitive configuration data (e.g. passwords) may be logged in clear-text. This attack appear to be exploitable via victims with configuration matching a specific pattern will observe sensitive data outputted in their service log files. This vulnerability appears to have been fixed in 1.2.1 and later, after commit 46ff10023e8cbf1b6978838f47c51b20b98fe30b.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2018-1000060?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `sensu` | Red Hat:openstack-optools:10::el7 | All versions | 0:0.23.2-4.el7ost |
| `sensu` | Red Hat:openstack-optools:11::el7 | All versions | 0:0.27.0-4.el7ost |
| `sensu-common` | Red Hat:openstack-optools:11::el7 | All versions | 0:0.27.0-4.el7ost |
| `sensu` | Red Hat:openstack-optools:12::el7 | All versions | 0:0.27.0-4.el7ost |
| `sensu-common` | Red Hat:openstack-optools:12::el7 | All versions | 0:0.27.0-4.el7ost |

Products: Sensu Sensu Core.

## How do I fix CVE-2018-1000060?

Upgrade to a fixed version.

## Is CVE-2018-1000060 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2018-1000209](https://insights.sbomify.com/CVE-2018-1000209/): Privilege escalation in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-1000060 and fix it if it is affected.

What it is: CVE-2018-1000060 is a critical vulnerability in n/a, published on 9 Feb 2018. 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-2018-1000060 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-2018-1000060/ (Markdown: https://insights.sbomify.com/CVE-2018-1000060/index.md)
```

## Sources

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

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