# CVE-2024-56514: Karmada Tar Slips in CRDs archive extraction

> Attackers can write arbitrary files via malicious CRD archives during Karmada initialization, potentially leading to code execution or data modification.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 3 Jan 2025
- **Updated:** 3 Jan 2025
- **Also known as:** GHSA-cwrh-575j-8vr3, GO-2025-3363

## What is CVE-2024-56514?

CVE-2024-56514 is a medium-severity path traversal vulnerability in karmada-io karmada, published on 3 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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, 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. From Karmada version 1.12.0, when processing custom CRDs files, CRDs archive verification is utilized to enhance file system robustness. A workaround is available. Someone who needs to set flag `--crd` to customize the CRD files required for Karmada initialization when using `karmadactl init` to set up Karmada 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, one must upgrade one's karmada-operator to one of the fixed versions.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-56514?

3 open source packages ship an affected version, including github.com/karmada-io/karmada.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/karmada-io/karmada` | Go | All versions | 1.12.0 |
| `github.com/karmada-io/karmada` | Go | All versions | 1.12.0 |
| `github.com/karmada-io/karmada` | Go | All versions | 1.12.0 |

## How do I fix CVE-2024-56514?

Upgrade github.com/karmada-io/karmada to 1.12.0 or later.

## Is CVE-2024-56514 being exploited?

There is no known exploitation of CVE-2024-56514 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-56514 and fix it if it is affected.

What it is: CVE-2024-56514 is a medium-severity path traversal vulnerability in karmada-io karmada, published on 3 Jan 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-56514 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/karmada-io/karmada (Go): affected all versions; fixed in 1.12.0
- github.com/karmada-io/karmada (Go): affected all versions; fixed in 1.12.0
- github.com/karmada-io/karmada (Go): affected all versions; fixed in 1.12.0

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-56514/ (Markdown: https://insights.sbomify.com/CVE-2024-56514/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-56514
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-56514
- OSV: https://osv.dev/vulnerability/CVE-2024-56514

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-56514/
Summaries are generated and may contain mistakes; the official description above is the record.