Security readout for executives and security teams
Plain-English summary
Red Hat OpenShift Enterprise 3.1 could leave the master configuration file readable by local users. If that file contains Active Directory credentials, a local account on the system could expose credentials useful for broader access.
Executive priority
Prioritize affected OpenShift 3.1 environments that integrate with Active Directory. The main business risk is credential exposure leading to follow-on access, but available evidence does not show active exploitation.
Technical view
The issue is world-readable permissions on /etc/origin/master/master-config.yaml in OpenShift Enterprise 3.1. The CVE description says local users can obtain Active Directory credentials by reading the file. The source bundle does not provide CVSS, CWE, or exact fixed package details.
Likely exposure
Exposure is most likely where OpenShift Enterprise 3.1 is deployed and master-config.yaml contains Active Directory credentials. The attacker must already have local user access to the relevant system.
Exploitation context
The source bundle does not cite active exploitation, and KEV is false. This is a local credential disclosure risk, not evidence of remote exploitation by itself.
Researcher notes
Evidence is limited to the CVE description and Red Hat advisory reference. No CVSS, CWE, exploit status, or precise fixed versions were included in the provided bundle, so validate details against RHSA-2016:1038.
Mitigation direction
- Review Red Hat advisory RHSA-2016:1038 for vendor-supported remediation.
- Apply the vendor-recommended OpenShift Enterprise 3.1 updates or configuration changes.
- Restrict access to master-config.yaml according to vendor guidance.
- Rotate exposed Active Directory credentials if unauthorized readability is confirmed.
Validation and detection
- Identify OpenShift Enterprise 3.1 systems in the environment.
- Check whether master-config.yaml contains Active Directory credentials.
- Verify unprivileged local users cannot read master-config.yaml.
- Confirm deployed packages align with RHSA-2016:1038 guidance.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2016-2142 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- RHSA-2016:1038CVE reference · vendor-advisory, x_refsource_REDHAT
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.