Skip to content
Fencer Vulns
medium 6.5

CVE-2023-30617 json

Leverage the kruise-daemon pod to list all secrets in the entire cluster

published 2024-01-03 2 y ago modified 2026-09-10 1 mo ago also GHSA-437m-7hj5-9mpw , EUVD-2024-0237

cvss
6.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 42%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/openkruise/kruise 1.3.1, 1.4.1, 1.5.2
  • openkruise kruise 1.3.1, 1.4.1, 1.5.2

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
16 mo ago

Exploit prediction

0.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CNA 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N
GitHub 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:N

Affected packages

ecosystem package affected fixed in
go github.com/openkruise/kruise
>=0.8.0, <1.3.1
>=1.4.0, <1.4.1
>=1.5.0, <1.5.2
1.3.1
1.4.1
1.5.2

Affected products

  • openkruise kruise

Classification

Weakness
  • CWE-250 Execution with Unnecessary Privileges
  • CWE-269 Improper Privilege Management

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.