CVE-2023-30617

Kruise allows leveraging the kruise-daemon pod to list all secrets in the entire cluster

Workarounds

For users that do not require imagepulljob functions, they can modify kruise-daemon-role to drop the cluster level secret get/list privilege

References

None

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.

The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access. Typical impact: privilege escalation beyond the intended level.

CVE-2023-30617 has a CVSS score of 6.5 (Medium). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.3.1, 1.4.1, 1.5.2); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

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

1. What is CVE-2023-30617? CVE-2023-30617 is a medium-severity improper privilege management vulnerability in github.com/openkruise/kruise (go), affecting versions >= 0.8.0, < 1.3.1. It is fixed in 1.3.1, 1.4.1, 1.5.2. The application assigns, modifies, tracks, or checks privileges incorrectly, allowing a user to gain elevated access.
2. How severe is CVE-2023-30617? CVE-2023-30617 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of github.com/openkruise/kruise are affected by CVE-2023-30617? github.com/openkruise/kruise (go) versions >= 0.8.0, < 1.3.1 is affected.
4. Is there a fix for CVE-2023-30617? Yes. CVE-2023-30617 is fixed in 1.3.1, 1.4.1, 1.5.2. Upgrade to this version or later.
5. Is CVE-2023-30617 exploitable, and should I be worried? Whether CVE-2023-30617 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2023-30617 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2023-30617?
   • Upgrade github.com/openkruise/kruise to 1.3.1 or later
   • Upgrade github.com/openkruise/kruise to 1.4.1 or later
   • Upgrade github.com/openkruise/kruise to 1.5.2 or later

Other vulnerabilities in github.com/openkruise/kruise