An authentication bypass vulnerability was discovered in kube-apiserver. This issue could allow a remote, authenticated attacker who has been given permissions "update, patch" the "pods/ephemeralcontainers" subresource beyond what the default is. They would then need to create a new pod or patch one that they already have access to. This might allow evasion of SCC admission restrictions, thereby gaining control of a privileged pod.
Workaround:
The product requires authentication, but the product has an alternate path or channel that does not require authentication.
Link | Tags |
---|---|
https://access.redhat.com/errata/RHSA-2023:3976 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2023:4093 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2023:4312 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2023:4898 | third party advisory vendor advisory |
https://access.redhat.com/errata/RHSA-2023:5008 | vendor advisory |
https://access.redhat.com/security/cve/CVE-2023-1260 | third party advisory vdb entry |
https://bugzilla.redhat.com/show_bug.cgi?id=2176267 | third party advisory issue tracking |
https://github.com/advisories/GHSA-92hx-3mh6-hc49 | |
https://security.netapp.com/advisory/ntap-20231020-0010/ | third party advisory |