[Security Advisory] CVE-2023-2431: Bypass of seccomp profile enforcement

Vellore Rajakumar, Sri Saran Balaji

unread,

Jun 14, 2023, 11:41:49 PM6/14/23

to kubernete...@googlegroups.com, d...@kubernetes.io, kubernetes-sec...@googlegroups.com, kubernetes-se...@googlegroups.com, distributo...@kubernetes.io, kubernetes+a...@discoursemail.com

Hello Kubernetes Community,

A security issue was discovered in Kubelet that allows pods to bypass the seccomp profile enforcement. This issue has been rated LOW (CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:N) (score: 3.4)

Am I vulnerable?

If you have pods in your cluster that use localhost type for seccomp profile but specify an empty profile, then you are affected by this issue. In this scenario, this vulnerability allows the pod to run in “unconfined” (seccomp disabled) mode. This bug affects Kubelet.

Affected Versions

v1.27.0 - v1.27.1
v1.26.0 - v1.26.4
v1.25.0 - v1.25.9
<= v1.24.13

How do I remediate this vulnerability?

To remediate this vulnerability, you should upgrade your Kubelet to one of the below mentioned versions.

Fixed Versions

This issue is fixed in the following versions:

v1.27.2
v1.26.5
v1.25.10
V1.24.14

To upgrade, refer to the documentation: https://kubernetes.io/docs/tasks/administer-cluster/cluster-upgrade/

Acknowledgements

This vulnerability was reported by Tim Allclair, and fixed by Craig Ingram.

Thank You,

Balaji on behalf of the Kubernetes Security Response Committee

Sean McGinnis

unread,

Jun 15, 2023, 9:14:36 AM6/15/23

to kubernetes-se...@googlegroups.com

Thank you for the notification. It appears the CVE number in the title is not correct, and there is no link to the report. Do you have a reference with more information?

Also, it appears the "localhost type" link goes to a 404 page.

Thanks!

Sean

--
You received this message because you are subscribed to the Google Groups "dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dev+uns...@kubernetes.io.
To view this discussion on the web visit https://groups.google.com/a/kubernetes.io/d/msgid/dev/E4AB32C0-AC03-4648-B16C-076B964EA9FB%40amazon.com.

Vellore Rajakumar, Sri Saran Balaji

unread,

Jun 15, 2023, 10:59:08 AM6/15/23

to kubernetes-security-discuss

Thank you Sean for reporting this. CVE details are not yet published to CVE service, should be completed in next hour or so. The Security Response Committee does not usually provide full reproduction steps for vulnerabilities, but for this case I have added the details to https://github.com/kubernetes/kubernetes/issues/118690 with sample spec and updated the broken link. Thank you again!!