Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2024-42480

HIGH

CVE-2024-42480 is a high-severity (CVSS 8.1) CWE-284 vulnerability in github.com/clastix/kamaji. 1 public exploit reference exists, so weaponization risk is real. O3 Security confirms whether CVE-2024-42480 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Kamaji's RBAC Roles for `etcd` are not disjunct

Also known asGHSA-6r4j-4rjc-8vw5GO-2024-3063
Published
Aug 12, 2024
Updated
Jul 15, 2026
Affected
1 pkg
Patched
None yet
Exploits
1 known

Blast Radius

1 pkg affected
🐹github.com/clastix/kamaji

Real-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

Kamaji is the Hosted Control Plane Manager for Kubernetes. In versions 1.0.0 and earlier, Kamaji uses an "open at the top" range definition in RBAC for etcd roles leading to some TCPs API servers being able to read, write, and delete the data of other control planes. This vulnerability is fixed in edge-24.8.2.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/clastix/kamajiall versionsNo fix
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/clastix/kamaji. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Remediation status

    No patched version of github.com/clastix/kamaji has shipped for CVE-2024-42480 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2024-42480 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2024-42480. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Kamaji is the Hosted Control Plane Manager for Kubernetes. In versions 1.0.0 and earlier, Kamaji uses an "open at the top" range definition in RBAC for etcd roles leading to some TCPs API servers being able to read, write, and delete the data of other control planes. This vulnerability is fixed in edge-24.8.2.
O3 Security · Impact-Aware SCA

Is CVE-2024-42480 in your dependencies?

O3 detects CVE-2024-42480 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.