Incorrect Privilege Assignment Affecting govulncheck-vulndb package, versions <0.0.20250108T191942-150000.1.26.1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Incorrect Privilege Assignment vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-SLES156-GOVULNCHECKVULNDB-8620218
- published13 Jan 2025
- disclosed10 Jan 2025
Introduced: 10 Jan 2025
CVE-2024-56513 (opens in a new tab)How to fix?
Upgrade SLES:15.6 govulncheck-vulndb to version 0.0.20250108T191942-150000.1.26.1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream govulncheck-vulndb package and not the govulncheck-vulndb package as distributed by SLES.
See How to fix? for SLES:15.6 relevant fixed versions and status.
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.
References
- https://www.suse.com/security/cve/CVE-2024-56513.html
- https://github.com/karmada-io/karmada/commit/2c82055c4c7f469411b1ba48c4dba4841df04831
- https://github.com/karmada-io/karmada/pull/5793
- https://github.com/karmada-io/karmada/security/advisories/GHSA-mg7w-c9x2-xh7r
- https://karmada.io/docs/administrator/security/component-permission