CVE-2023-30617 — kruise
MEDIUMCVE-2023-30617 is a medium-severity (CVSS 6.5) CWE-250 vulnerability in github.com/openkruise/kruise. A fix is available for github.com/openkruise/kruise — see the affected versions and patch details below.
Leverage the kruise-daemon pod to list all secrets in the entire cluster
Exploitation Status
No confirmed exploitation observed yet
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2023-30617.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/openkruise/kruise🐹github.com/openkruise/kruise🐹github.com/openkruise/kruiseReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Impact
Attacker that has gain 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, attackers can leverage the "captured" secrets (e.g. the kruise-manager service account token) to gain extra privilege such as pod modification.
Workarounds
For users that do not require imagepulljob functions, they can modify kruise-daemon-role to drop the cluster level secret get/list privilege
Patches
For users who're using v0.8.x ~ v1.2.x, please update the v1.3.1 For users who're using v1.3, please update the v1.3.1 For users who're using v1.4, please update the v1.4.1 For users who're using v1.5, please update the v1.5.2
References
None
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/openkruise/kruise | ≥ 0.8.0&&< 1.3.1 | 1.3.1go get github.com/openkruise/kruise@v1.3.1 |
| 🐹Go | github.com/openkruise/kruise | ≥ 1.4.0&&< 1.4.1 | 1.4.1go get github.com/openkruise/kruise@v1.4.1 |
| 🐹Go | github.com/openkruise/kruise | ≥ 1.5.0&&< 1.5.2 | 1.5.2go get github.com/openkruise/kruise@v1.5.2 |
Affected Products
kruiseopenkruiseDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/openkruise/kruise, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/openkruise/kruise to 1.3.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2023-30617 is resolved across your whole dependency graph.
Workarounds
Close the privilege gap rather than the entry point: audit which accounts, roles and service identities can reach the affected operation, drop the component to the least privilege it actually needs, and review file and directory permissions created by earlier installs — a default left in place is what makes this reachable.
Frequently Asked Questions
Is CVE-2023-30617 in your dependencies?
Find it across Go, including transitive dependencies.