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

607 views
Skip to first unread message

Vellore Rajakumar, Sri Saran Balaji

unread,
Jun 14, 2023, 11:41:51 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

 

Reply all
Reply to author
Forward
0 new messages