github.com/karmada-io/karmada vulnerabilities

Registry
Go
Latest
1.19.1

8 known advisories

The latest version, 1.19.1, is affected by 1 of them.

Is your project on an affected github.com/karmada-io/karmada?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Go apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Security advisories for github.com/karmada-io/karmada

  • LowCVE-2024-56514GO-2025-33637 Jan 2025

    Karmada Tar Slips in CRDs archive extraction in github.com/karmada-io/karmada

    Affected
    <1.12.0
    Fixed in
    1.12.0
  • LowCVE-2024-56513GO-2025-33647 Jan 2025

    Karmada PULL Mode Cluster Privilege Escalation in github.com/karmada-io/karmada

    Affected
    <1.12.0
    Fixed in
    1.12.0
  • MediumCVE-2024-56514GHSA-cwrh-575j-8vr33 Jan 2025

    Karmada Tar Slips in CRDs archive extraction

    Affected
    <1.12.0
    Fixed in
    1.12.0
  • HighCVE-2024-56513GHSA-mg7w-c9x2-xh7r3 Jan 2025

    Karmada PULL Mode Cluster Privilege Escalation

    Affected
    <1.12.0
    Fixed in
    1.12.0
  • LowGO-2024-244128 Jun 2024

    The DES/3DES cipher was used as part of the TLS protocol by installation tools in github.com/karmada-io/karmada

    Affected
    <1.8.0
    Fixed in
    1.8.0
  • LowCVE-2024-33396GO-2024-28175 Jun 2024

    karmada vulnerable to arbitrary code execution via a crafted command in github.com/karmada-io/karmada

    Affected
    All versions
    Fixed in
    No fix released
  • HighCVE-2024-33396GHSA-wccg-v638-j9q22 May 2024

    karmada vulnerable to arbitrary code execution via a crafted command

    Affected
    <=1.9.0
    Fixed in
    No fix released
  • LowGHSA-7xg2-83f8-39mr3 Jan 2024

    The DES/3DES cipher was used as part of the TLS protocol by installation tools

    Affected
    <1.8.0
    Fixed in
    1.8.0

Is your github.com/karmada-io/karmada version vulnerable?

Which of your client projects still run an old github.com/karmada-io/karmada?

NPMscan reads the go.mod in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.

Other Go packages

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Go registry.