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

> Local users can read world-readable configuration files to steal Active Directory credentials in Red Hat OpenShift Enterprise.

- **Severity:** Medium 5.5 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jun 2016
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8qr6-wfrg-m44g, RHSA-2016:1038

## What is CVE-2016-2142?

CVE-2016-2142 is a medium-severity vulnerability in Redhat Openshift, published on 8 Jun 2016. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Red Hat OpenShift Enterprise 3.1 uses world-readable permissions on the /etc/origin/master/master-config.yaml configuration file, which allows local users to obtain Active Directory credentials by reading the file.

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

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

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `atomic-openshift` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `atomic-openshift-clients` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `atomic-openshift-clients-redistributable` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `atomic-openshift-dockerregistry` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `atomic-openshift-master` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `atomic-openshift-node` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `atomic-openshift-pod` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `atomic-openshift-recycle` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `atomic-openshift-sdn-ovs` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |
| `tuned-profiles-atomic-openshift-node` | Red Hat:openshift:3.1::el7 | All versions | 0:3.1.1.6-6.git.43.f583589.el7aos |

Products: Redhat Openshift.

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

Apply the vendor's patch.

## Is CVE-2016-2142 being exploited?

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

## Other vulnerabilities in Redhat Openshift

- [CVE-2014-3496](https://insights.sbomify.com/CVE-2014-3496/): Command injection in n/a (critical 10.0)
- [CVE-2014-0234](https://insights.sbomify.com/CVE-2014-0234/): Hardcoded credentials in Red Hat OpenShift Enterprise (critical 9.8)
- [CVE-2013-2060](https://insights.sbomify.com/CVE-2013-2060/): Command injection in OpenShift Origin (critical 9.8)
- [CVE-2013-4561](https://insights.sbomify.com/CVE-2013-4561/): Path traversal in openshift-origin-msg-node-mcollective (critical 9.1)
- [CVE-2014-0163](https://insights.sbomify.com/CVE-2014-0163/): Command injection in Openshift (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-2142 is a medium-severity vulnerability in Redhat Openshift, published on 8 Jun 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-2142 in the wild and no public exploit code.

Affected product: Redhat Openshift. 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-2142/ (Markdown: https://insights.sbomify.com/CVE-2016-2142/index.md)
```

## Sources

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

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