Kubernetes kube-apiserver allows access to custom resources via wrong scope
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Kubernetes | Kubernetes | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 3.10 | |||
| atomic-openshift-0:3.10.170-1.git.0.8e592d6.el7 | cpe:/a:redhat:openshift:3.10::el7 | RHSA-2019:2690 | 2019-09-12T00:00:00Z |
| Red Hat OpenShift Container Platform 3.11 | |||
| ansible-service-broker-1:1.3.23-2.el7 | cpe:/a:redhat:openshift:3.11::el7 | RHBA-2019:2816 | 2019-09-24T00:00:00Z |
| Red Hat OpenShift Container Platform 3.9 | |||
| ansible-service-broker-0:1.1.20-2.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| atomic-openshift-0:3.9.101-1.git.0.150f595.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| atomic-openshift-descheduler-0:3.9.13-2.git.267.bb59a3f.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| atomic-openshift-dockerregistry-0:3.9.101-1.git.1.13625cf.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| atomic-openshift-node-problem-detector-0:3.9.13-2.git.167.5d6b0d4.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| atomic-openshift-web-console-0:3.9.101-1.git.1.601c6d2.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| cockpit-0:195-2.rhaos.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| containernetworking-plugins-0:0.5.2-6.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| cri-o-0:1.9.16-3.git858756d.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| cri-tools-0:1.0.0-6.rhaos3.9.git8e6013a.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| golang-github-openshift-oauth-proxy-0:2.1-3.git885c9f40.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| golang-github-openshift-prometheus-alert-buffer-0:0-3.gitceca8c1.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| golang-github-prometheus-alertmanager-0:0.14.0-2.git30af4d0.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| golang-github-prometheus-node_exporter-0:3.9.101-1.git.1.8295224.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| golang-github-prometheus-prometheus-0:2.2.1-2.gitbc6058c.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| golang-github-prometheus-promu-0:0-5.git85ceabc.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| hawkular-openshift-agent-0:1.2.2-3.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| heapster-0:1.3.0-4.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| image-inspector-0:2.1.3-2.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| openshift-enterprise-image-registry-0:3.8.0-2.git.216.b6b90bb.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| openshift-eventrouter-0:0.1-3.git5bd9251.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| openshift-external-storage-0:0.0.1-9.git78d6339.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| openvswitch-ovn-kubernetes-0:0.1.0-3.el7 | cpe:/a:redhat:openshift:3.9::el7 | RHSA-2019:2769 | 2019-10-24T00:00:00Z |
| Red Hat OpenShift Container Platform 4.1 | |||
| openshift-0:4.1.10-201908060758.git.0.d81afa6.el8 | cpe:/a:redhat:openshift:4.1::el7 | RHSA-2019:2504 | 2019-08-15T00:00:00Z |
No data available yet.
Vendor Workaround
To mitigate, remove authorization rules that grant access to cluster-scoped resources within namespaces. For example, RBAC roles and clusterroles intended to be referenced by namespaced rolebindings should not grant access to resources:[*], apiGroups:[*], or grant access to cluster-scoped custom resources.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2022-3812 | The Kubernetes kube-apiserver mistakenly allows access to a cluster-scoped custom resource if the request is made as if the resource were namespaced. Authorizations for the resource accessed in this manner are enforced using roles and role bindings within the namespace, meaning that a user with access only to a resource in one namespace could create, view update or delete the cluster-scoped resource (according to their namespace role privileges). Kubernetes affected versions include versions prior to 1.13.9, versions prior to 1.14.5, versions prior to 1.15.2, and versions 1.7, 1.8, 1.9, 1.10, 1.11, 1.12. |
Github GHSA |
GHSA-fp37-c92q-4pwq | Kubernetes kube-apiserver unauthorized access |
No CVSS v4.0
This CVE is not in the KEV list.
Exploit prediction score: 2.1% (2.150% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.