A vulnerability was found in openkruise Kruise up to 1.3.0/1.4.0/1.5.1. It has been classified as problematic. This affects an unknown functionality of the component kruise-daemon pod. The manipulation with an unknown input leads to a unnecessary privileges vulnerability. CWE is classifying the issue as CWE-250. The product performs an operation at a privilege level that is higher than the minimum level required, which creates new weaknesses or amplifies the consequences of other weaknesses. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:

Kruise provides automated management of large-scale applications on Kubernetes. Starting in version 0.8.0 and prior to versions 1.3.1, 1.4.1, and 1.5.2, an attacker who has gained root privilege of the node that kruise-daemon run can leverage the kruise-daemon pod to list all secrets in the entire cluster. After that, the attacker can leverage the "captured" secrets (e.g. the kruise-manager service account token) to gain extra privileges such as pod modification. Versions 1.3.1, 1.4.1, and 1.5.2 fix this issue. A workaround is available. For users that do not require imagepulljob functions, they can modify kruise-daemon-role to drop the cluster level secret get/list privilege.

The weakness was released 01/03/2024. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-30617 since 04/13/2023. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1068 for this issue.

Upgrading to version 1.3.1, 1.4.1 or 1.5.2 eliminates this vulnerability.

Productinfo

Vendor

• openkruise

Name

• Kruise

Version

• 1.0
• 1.1
• 1.2
• 1.3
• 1.4
• 1.5.0
• 1.5.1

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Discussion