{"answers":{"affected":"3 open source packages ship an affected version, including github.com/karmada-io/karmada.","exploited":"There is no known exploitation of CVE-2024-56513 in the wild and no public exploit code.","fix":"Upgrade github.com/karmada-io/karmada to 1.12.0 or later.","what":"CVE-2024-56513 is a high-severity vulnerability in karmada-io karmada, published on 3 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2024-56513 and fix it if it is affected.\n\nWhat it is: CVE-2024-56513 is a high-severity vulnerability in karmada-io karmada, published on 3 Jan 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2024-56513 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- github.com/karmada-io/karmada (Go): affected all versions; fixed in 1.12.0\n- github.com/karmada-io/karmada (Go): affected all versions; fixed in 1.12.0\n- github.com/karmada-io/karmada (Go): affected all versions; fixed in 1.12.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-56513/ (Markdown: https://insights.sbomify.com/CVE-2024-56513/index.md)","id":"CVE-2024-56513","markdown":"https://insights.sbomify.com/CVE-2024-56513/index.md","name":"CVE-2024-56513","record":{"aliases":["GHSA-mg7w-c9x2-xh7r","GO-2025-3364"],"analysis":{"component_type":"container_or_infrastructure","fix_type":"upgrade","impacts":["privilege_escalation","code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Kubernetes management system","requires_auth":"low_privilege","summary":"An attacker authenticating as karmada-agent can escalate privileges to control the entire Karmada federation and all member clusters.","user_interaction":"not_required","vuln_class":"privilege_escalation"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-266","name":"Incorrect Privilege Assignment"}],"description":"Karmada is a Kubernetes management system that allows users to run cloud-native applications across multiple Kubernetes clusters and clouds. Prior to version 1.12.0, the PULL mode clusters registered with the `karmadactl register` command have excessive privileges to access control plane resources. By abusing these permissions, an attacker able to authenticate as the karmada-agent to a karmada cluster would be able to obtain administrative privileges over the entire federation system including all registered member clusters. Since Karmada v1.12.0, command `karmadactl register` restricts the access permissions of pull mode member clusters to control plane resources. This way, an attacker able to authenticate as the karmada-agent cannot control other member clusters in Karmada. As a workaround, one may restrict the access permissions of pull mode member clusters to control plane resources according to Karmada Component Permissions Docs.","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":"Karmada PULL Mode Cluster Privilege Escalation","id":"CVE-2024-56513","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Go","product":null,"products":[],"type":"privilege_escalation","year":"2024"},"n_packages":3,"n_references":4,"next":{"headline":"Karmada Tar Slips in CRDs archive extraction","id":"CVE-2024-56514"},"packages":[{"ecosystem":"Go","fixed":["1.12.0"],"introduced":["0"],"last_affected":[],"package":"github.com/karmada-io/karmada","purl":null,"source":"GHSA-mg7w-c9x2-xh7r"},{"ecosystem":"Go","fixed":["1.12.0"],"introduced":["0"],"last_affected":[],"package":"github.com/karmada-io/karmada","purl":"pkg:golang/github.com/karmada-io/karmada","source":"GHSA-mg7w-c9x2-xh7r"},{"ecosystem":"Go","fixed":["1.12.0"],"introduced":["0"],"last_affected":[],"package":"github.com/karmada-io/karmada","purl":"pkg:golang/github.com/karmada-io/karmada","source":"GO-2025-3364"}],"prev":{"headline":"Apache NiFi: Missing Complete Authorization for Parameter and Service References","id":"CVE-2024-56512"},"products":["karmada"],"published":"2025-01-03","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":"total"},"state":"PUBLISHED","updated":"2025-01-03","vendors":["karmada-io"]},"summary":"An attacker authenticating as karmada-agent can escalate privileges to control the entire Karmada federation and all member clusters.","url":"https://insights.sbomify.com/CVE-2024-56513/"}