{"answers":{"affected":"3 open source packages ship an affected version, including github.com/kubean-io/kubean.","exploited":"There is no known exploitation of CVE-2024-41820 in the wild and no public exploit code.","fix":"Upgrade github.com/kubean-io/kubean to 0.18.0 or later.","what":"CVE-2024-41820 is a medium-severity vulnerability in kubean-io kubean, published on 5 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-41820 and fix it if it is affected.\n\nWhat it is: CVE-2024-41820 is a medium-severity vulnerability in kubean-io kubean, published on 5 Aug 2024. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-41820 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/kubean-io/kubean (Go): affected all versions; fixed in 0.18.0\n- github.com/kubean-io/kubean (Go): affected all versions; fixed in 0.18.0\n- github.com/kubean-io/kubean (Go): affected all versions; fixed in 0.18.0\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2024-41820/ (Markdown: https://insights.sbomify.com/CVE-2024-41820/index.md)","id":"CVE-2024-41820","markdown":"https://insights.sbomify.com/CVE-2024-41820/index.md","name":"CVE-2024-41820","record":{"aliases":["GHSA-3wfj-3x8q-hrpg","GO-2024-3039"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes cluster management","requires_auth":"high_privilege","summary":"Malicious users with worker node access can escalate privileges to control the entire Kubernetes cluster due to excessive RBAC permissions.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":6,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:H","version":"3.1"},"cwes":[{"id":"CWE-732","name":"Incorrect Permission Assignment for Critical Resource"}],"description":"Kubean is a cluster lifecycle management toolchain based on kubespray and other cluster LCM engine. The ClusterRole has `*` verbs of `*` resources. If a malicious user can access the worker node which has kubean's deployment, he/she can abuse these excessive permissions to do whatever he/she likes to the whole cluster, resulting in a cluster-level privilege escalation. This issue has been addressed in release version 0.18.0. Users are advised to upgrade. There are no known workarounds for this vulnerability.","ecosystems":["Go"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Cluster-level privilege escalation in kubean","id":"CVE-2024-41820","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":3,"n_references":3,"next":{"headline":"Information disclosure in TeamCity","id":"CVE-2024-41824"},"packages":[{"ecosystem":"Go","fixed":["0.18.0"],"introduced":["0"],"last_affected":[],"package":"github.com/kubean-io/kubean","purl":null,"source":"GHSA-3wfj-3x8q-hrpg"},{"ecosystem":"Go","fixed":["0.18.0"],"introduced":["0"],"last_affected":[],"package":"github.com/kubean-io/kubean","purl":"pkg:golang/github.com/kubean-io/kubean","source":"GHSA-3wfj-3x8q-hrpg"},{"ecosystem":"Go","fixed":["0.18.0"],"introduced":["0"],"last_affected":[],"package":"github.com/kubean-io/kubean","purl":"pkg:golang/github.com/kubean-io/kubean","source":"GO-2024-3039"}],"prev":{"headline":"Note Mark has a stored XSS in the note link href attribute","id":"CVE-2024-41819"},"products":["kubean"],"published":"2024-08-05","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"Go Vulnerability Database","prefix":"GO"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2024-08-06","vendors":["kubean-io"]},"summary":"Malicious users with worker node access can escalate privileges to control the entire Kubernetes cluster due to excessive RBAC permissions.","url":"https://insights.sbomify.com/CVE-2024-41820/"}