CVE-2024-39690 is a high-severity incorrect authorization vulnerability in github.com/projectcapsule/capsule (go), affecting versions <= 0.7.0. It is fixed in 0.7.1.
Attack Vector Then, let me briefly explain the reasons for the errors mentioned above: 1. The 'kubectl edit' command was used to patch the namespace, but this operation requires both 'get' and 'patch' permissions, hence the error. One should use methods like 'curl' to directly send a PATCH request; 2. The webhook does not intercept patch operations on 'kube-system' because 'kube-system' does not have an ownerReference. Below are my detailed reproduction steps Create a test cluster kind create cluster --image=kindest/node:v1.24.15 --name=k8s Install the capsule helm install capsule projectcapsule/capsule -n capsule-system --create-namespace Create a tenant Create user alice Patch kube-system (The first command is executed in the current shell, while the 2nd and 3rd commands require a different shell window because the current shell is being used as a proxy.) Check the result The kube-system is patched successfully. Summary The tenant-owner can patch any arbitrary namespace that has not been taken over by a tenant (i.e., namespaces without the ownerReference field), thereby gaining control of that namespace. I would like to express my apologies once again. I have always been sincere in my research and communication, and I did not intend to disturb you on purpose.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
CVE-2024-39690 has a CVSS score of 8.4 (High). The vector is reachable from an adjacent network, low privileges required, and user interaction required. 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 (0.7.1). Upgrading removes the vulnerable code path.
go
github.com/projectcapsule/capsule (<= 0.7.0)github.com/projectcapsule/capsule → 0.7.1 (go)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
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 instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2024-39690 is reachable in your applications. Explore open-source security for your team.
See if CVE-2024-39690 is reachable in your applications. Get a demo
Upgrade github.com/projectcapsule/capsule to 0.7.1 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2024-39690 is a high-severity incorrect authorization vulnerability in github.com/projectcapsule/capsule (go), affecting versions <= 0.7.0. It is fixed in 0.7.1. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
CVE-2024-39690 has a CVSS score of 8.4 (High). 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.
github.com/projectcapsule/capsule (go) versions <= 0.7.0 is affected.
Yes. CVE-2024-39690 is fixed in 0.7.1. Upgrade to this version or later.
Whether CVE-2024-39690 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
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.
Upgrade github.com/projectcapsule/capsule to 0.7.1 or later.