OpenshiftApplication · Redhat
CVE-2016-2142
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedRed 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe OpenShift Enterprise 3.1 master configuration file (/etc/origin/master/master-config.yaml) is stored with world-readable permissions, allowing any local user on the system to read the file and extract embedded Active Directory credentials used for authentication.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
OpenshiftApplication
= 3.1CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm OpenShift Enterprise 3.1 is installedCheck for the presence of /etc/origin/master/master-config.yaml or run 'rpm -q openshift-enterprise' to verify the product is installedAffected if The file /etc/origin/master/master-config.yaml exists and the system runs OpenShift Enterprise version 3.1
-
Inspect file permissions on master-config.yamlRun 'ls -la /etc/origin/master/master-config.yaml' to view the permission bitsAffected if The file permissions show 'r--r--r--' (644) or any other world-readable setting (e.g., o+r), allowing any local user to read the file
-
Test read access as non-privileged userAs a non-root user (e.g., using a standard user account), run 'cat /etc/origin/master/master-config.yaml' or 'test -r /etc/origin/master/master-config.yaml && echo readable'Affected if The file can be read successfully by a non-privileged user account without sudo
-
Verify file ownership and groupRun 'stat -c '%U:%G %a' /etc/origin/master/master-config.yaml' to check owner and permission bits in numeric formatAffected if The permissions include read access for 'others' (the last digit is 4 or higher, e.g., 644, 644, 664, etc.)
If /etc/origin/master/master-config.yaml exists, is version 3.1, and has permissions that allow non-root users to read it (o+r or a+r), the environment is vulnerable to credential exposure.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataChange file permissions on /etc/origin/master/master-config.yaml to restrict read access to the root user and the openshift master service account (e.g., chmod 600 or chown root:openshift).
Fix this in Openshift
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-2142 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-2142 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data