What is CVE-2024-42480?

CVE-2024-42480 is a critical-severity security vulnerability in github.com/clastix/kamaji (go), affecting versions <= 1.0.0. No fixed version is listed yet.

How severe is CVE-2024-42480?

CVE-2024-42480 has a CVSS score of 8.1 (Critical). 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.

Which versions of github.com/clastix/kamaji are affected by CVE-2024-42480?

github.com/clastix/kamaji (go) versions <= 1.0.0 is affected.

Is there a fix for CVE-2024-42480?

No fixed version is listed for CVE-2024-42480 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2024-42480 exploitable, and should I be worried?

Whether CVE-2024-42480 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.

What actually determines whether CVE-2024-42480 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.

CVE-2024-42480 in github.com/clastix/kamaji

Q: How severe is CVE-2024-42480?

CVE-2024-42480 has a CVSS score of 8.1 (Critical). 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.

Q: Which versions of github.com/clastix/kamaji are affected by CVE-2024-42480?

github.com/clastix/kamaji (go) versions <= 1.0.0 is affected.

Q: Is there a fix for CVE-2024-42480?

No fixed version is listed for CVE-2024-42480 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2024-42480 exploitable, and should I be worried?

Whether CVE-2024-42480 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.

Q: What actually determines whether CVE-2024-42480 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.

Summary

RBAC Roles for etcd created by Kamaji are not disjunct

Using an "open at the top" range definition in RBAC for etcd roles leads to some TCPs API servers being able to read, write and delete the data of other control planes.

Details

The problematic code is this: https://github.com/clastix/kamaji/blob/8cdc6191242f80d120c46b166e2102d27568225a/internal/datastore/etcd.go#L19-L24

The range created by this RBAC setup code looks like this:

etcdctl role get example
Role example
KV Read:
	[/example/, \0)
KV Write:
	[/example/, \0)

The range end \0 means "everything that comes after" in etcd, so potentially all the key prefixes of controlplanes with a name that comes after "example" when sorting lexically (e.g. example1, examplf, all the way to zzzzzzz if you will).

PoC

Create two TCP in the same Namespace
Scale Kamaji to zero to avoid reconciliations
change the Kubernetes API Server --etcd-prefix flag value to point to the other TCP datastore key
wait it for get it up and running
use kubectl and will notice you're reading and writing data of another Tenant

Impact

Full control over other TCPs data, if you are able to obtain the name of other TCPs that use the same datastore and are able to obtain the user certificates used by your control plane (or you are able to configure the kube-apiserver Deployment, as shown in the PoC).

CVE-2024-42480 has a CVSS score of 8.1 (Critical). The vector is network-reachable, low 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. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

github.com/clastix/kamaji (<= 1.0.0)

Security releases

Not available

Kodem intelligence

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. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for CVE-2024-42480 yet.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2024-42480? CVE-2024-42480 is a critical-severity security vulnerability in github.com/clastix/kamaji (go), affecting versions <= 1.0.0. No fixed version is listed yet.
How severe is CVE-2024-42480? CVE-2024-42480 has a CVSS score of 8.1 (Critical). 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.
Which versions of github.com/clastix/kamaji are affected by CVE-2024-42480? github.com/clastix/kamaji (go) versions <= 1.0.0 is affected.
Is there a fix for CVE-2024-42480? No fixed version is listed for CVE-2024-42480 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2024-42480 exploitable, and should I be worried? Whether CVE-2024-42480 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
What actually determines whether CVE-2024-42480 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.