github.com/karmada-io/karmada
Affected
- introduced
0, fixed1.12.0(semver)
Fixed versions
1.12.0
Fix
- Fixed version
1.12.0go get github.com/karmada-io/[email protected]
Advisory
Also known as: CVE-2024-56514, GO-2025-3363
Karmada Tar Slips in CRDs archive extraction
Impact
_What kind of vulnerability is it? Who is impacted?_
Both in karmadactl and karmada-operator, it is possible to supply a filesystem path, or an HTTP(s) URL to retrieve the custom resource definitions(CRDs) needed by karmada. The CRDs are downloaded as a gzipped tarfile and are vulnerable to a TarSlip vulnerability. An attacker able to supply a malicious CRD file into a karmada initialization could write arbitrary files in arbitrary paths of the filesystem.
Patches
_Has the problem been patched? What versions should users upgrade to?_
From karmada version v1.12.0, when processing custom CRDs files, CRDs archive verification is utilized to enhance file system robustness.
Workarounds
_Is there a way for users to fix or remediate the vulnerability without upgrading?_
When using karmadactl init to set up Karmada, if you need to set flag --crd to customize the CRD files required for karmada initialization, you can manually inspect the CRD files to check whether they contain sequences such as ../ that would alter file paths, to determine if they potentially include malicious files.
When using karmada-operator to set up Karmada, you must upgrade your karmada-operator to one of the fixed versions.
References
_Are there any links users can visit to find out more?_
Medium Basis: The source's own band: MODERATE
0, fixed 1.12.0 (semver)1.12.0
1.12.0go get github.com/karmada-io/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0