How severe is GHSA-7xg2-83f8-39mr?

No CVSS score has been assigned to GHSA-7xg2-83f8-39mr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-7xg2-83f8-39mr?

GHSA-7xg2-83f8-39mr affects the following packages: github.com/karmada-io/karmada (Go). Ecosystems affected: Go.

How do I fix GHSA-7xg2-83f8-39mr?

Update github.com/karmada-io/karmada to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7xg2-83f8-39mr is resolved across your whole dependency graph.

How do I detect GHSA-7xg2-83f8-39mr in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/karmada-io/karmada, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-7xg2-83f8-39mr if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-7xg2-83f8-39mr?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7xg2-83f8-39mr can be triaged on real exposure rather than presence alone.

Is GHSA-7xg2-83f8-39mr actively exploited in the wild?

No public exploit code has been indexed for GHSA-7xg2-83f8-39mr yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-7xg2-83f8-39mr published, and has it been updated?

GHSA-7xg2-83f8-39mr was published on January 3, 2024 and was last updated on June 28, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

Not in CISA KEV

GHSA-7xg2-83f8-39mr — karmada

Fix: karmada-io/karmada@98e655f

GHSA-7xg2-83f8-39mr is a security vulnerability in github.com/karmada-io/karmada. A fix is available for github.com/karmada-io/karmada — see the affected versions and patch details below.

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

Also known asGO-2024-2441

Published

Jan 3, 2024

Updated

Jun 28, 2024

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Jun 28, 2024 · OSV.dev, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/karmada-io/karmada

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Impact

What kind of vulnerability is it? Who is impacted?

The Karmada components deployed with karmadactl, karma-operator, and helm chart take Golang default cipher suites as part of the TLS protocol, which includes the insecure algorithm. Referring to https://github.com/golang/go/issues/41476#issuecomment-694914728, the 3DES algorithm vulnerability is very unlikely to be attacked. However, to address the concerns and to avoid being disturbed by the security scanner, Karmada has decided to limit the cipher suites to exclude the insecure 3DES algorithm and accordingly release this security advisory.

The components affected are：

karmada-apiserver
karmada-aggregated-apiserver
karmada-search
karmada-metrics-adapter
etcd

Patches

Has the problem been patched? What versions should users upgrade to?

From Karmada v1.8.0, when deploying Karmada with karmadactl, karma-operator, and helm chart, the default minimum TLS version of components(include karmada-apiserver, karmada-aggregated-apiserver, karmada-search, and karmada-metrics-adapter) would be set to TLS1.3 to get rid of the insecure algorithm, and set default cipher suites(TLS_RSA_WITH_AES_128_CBC_SHA,TLS_RSA_WITH_AES_256_CBC_SHA,TLS_RSA_WITH_AES_128_GCM_SHA256,TLS_RSA_WITH_AES_256_GCM_SHA384,TLS_AES_128_GCM_SHA256,TLS_AES_256_GCM_SHA384,TLS_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA,TLS_ECDHE_RSA_WITH_AES_256_CBC_SHA,TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_ECDSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256,TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305_SHA256,TLS_ECDHE_RSA_WITH_CHACHA20_POLY1305,TLS_ECDHE_ECDSA_WITH_CHACHA20_POLY1305) for etcd.

Workarounds

Is there a way for users to fix or remediate the vulnerability without upgrading?

By setting the --tls-min-version for the affected components to TLS 1.3, or explicitly setting the --cipher-suites to secure algorithms.

References

Are there any links users can visit to find out more?

Enhancements made from the Karmada community: https://github.com/karmada-io/karmada/issues/4191
Impact discussions from the Golang community: https://github.com/golang/go/issues/41476

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/karmada-io/karmada`	all versions	1.8.0`go get github.com/karmada-io/karmada@v1.8.0`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/karmada-io/karmada, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/karmada-io/karmada to 1.8.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7xg2-83f8-39mr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-7xg2-83f8-39mr can be triaged on real exposure rather than presence alone.

Tailored to GHSA-7xg2-83f8-39mr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact _What kind of vulnerability is it? Who is impacted?_ The Karmada components deployed with `karmadactl`, `karma-operator`, and `helm chart` take Golang default cipher suites as part of the TLS protocol, which includes the insecure algorithm. Referring to https://github.com/golang/go/issues/41476#issuecomment-694914728, the 3DES algorithm vulnerability is very unlikely to be attacked. However, to address the concerns and to avoid being disturbed by the security scanner, Karmada has decided to limit the cipher suites to exclude the insecure 3DES algorithm and accordingly release this

O3 Security · Impact-Aware SCA

Is GHSA-7xg2-83f8-39mr in your dependencies?

O3 Security finds GHSA-7xg2-83f8-39mr across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

GHSA-7xg2-83f8-39mr — karmada

Real-World Exposure

Description

Impact

Patches

Workarounds

References

Affected Packages

Detection & mitigation playbook

Detect

Fix

Workarounds

How O3 protects you

Frequently Asked Questions

Is GHSA-7xg2-83f8-39mr in your dependencies?