OpenshiftApplication · Redhat
CVE-2016-5392
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 · uneditedThe API server in Kubernetes, as used in Red Hat OpenShift Enterprise 3.2, in a multi tenant environment allows remote authenticated users with knowledge of other project names to obtain sensitive project and user information via vectors related to the watch-cache list.
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 · moderate confidenceThe Kubernetes API server in Red Hat OpenShift Enterprise 3.2 contains an information disclosure vulnerability in multi-tenant environments. Authenticated users who know the names of other projects can access sensitive project and user information through the watch-cache list, allowing unauthorized cross-tenant data exposure.
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.2CVSS 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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/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.
-
Verify OpenShift Enterprise versionRun 'oc version' or check the master node's installed version to confirm it is exactly version 3.2Affected if The installed version is Red Hat OpenShift Enterprise 3.2 exactly
-
Check if multi-tenant isolation is in useList existing projects using 'oc get projects' to determine if multiple projects (tenants) exist in the environmentAffected if Multiple projects exist, indicating a multi-tenant setup where cross-project access could be exploited
-
Confirm the watch-cache is accessible via APITest API access to list resources in projects other than your own using 'oc get <resource> --all-namespaces' or direct API calls to /api/v1/namespaces/<other-project>/<resource>Affected if An authenticated user can successfully list resources in namespaces/projects they should not have access to
-
Inspect RBAC policy configurationReview the openshift-specific RBAC resources: 'oc get rolebindings --all-namespaces' and 'oc get roles --all-namespaces' to check for overly permissive bindings that allow cross-project accessAffected if RoleBindings exist that grant users permissions to resources in namespaces they do not own
-
Check for default cluster role bindingsRun 'oc get clusterrolebindings' and examine if the 'system:authenticated' group has broad access to all namespacesAffected if Default cluster roles grant list/watch access across all namespaces to all authenticated users
A user is affected if they are running exactly OpenShift Enterprise 3.2 with multiple projects and RBAC policies that allow authenticated users to list or watch resources in namespaces outside their own.
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 dataImplement strict RBAC policies to prevent cross-project access, configure network policies to enforce tenant isolation, and restrict API access to only resources within the user's own projects.
Fix this in Openshift
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5392 — 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-5392 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