# GHSA-7xg2-83f8-39mr: The DES/3DES cipher was used as part of the TLS protocol by installation tools - **Severity:** Not scored - **Exploited in the wild:** Not known - **Fix available:** Yes - **Published:** 3 Jan 2024 - **Also known as:** GO-2024-2441 ## What is GHSA-7xg2-83f8-39mr? GHSA-7xg2-83f8-39mr is a vulnerability in github.com/karmada-io/karmada, published on 3 Jan 2024. ### Official 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?_ 1. Enhancements made from the Karmada community: https://github.com/karmada-io/karmada/issues/4191 2. Impact discussions from the Golang community: https://github.com/golang/go/issues/41476 ## Which versions are affected by GHSA-7xg2-83f8-39mr? 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.8.0 | | `github.com/karmada-io/karmada` | Go | All versions | 1.8.0 | | `github.com/karmada-io/karmada` | Go | All versions | 1.8.0 | ## How do I fix GHSA-7xg2-83f8-39mr? Upgrade github.com/karmada-io/karmada to 1.8.0 or later. ## Is GHSA-7xg2-83f8-39mr being exploited? There is no known exploitation of GHSA-7xg2-83f8-39mr in the wild and no public exploit code. ## Fix prompt for AI coding agents ```text Check this codebase for GHSA-7xg2-83f8-39mr and fix it if it is affected. What it is: GHSA-7xg2-83f8-39mr is a vulnerability in github.com/karmada-io/karmada, published on 3 Jan 2024. Exploitation: There is no known exploitation of GHSA-7xg2-83f8-39mr 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.8.0 - github.com/karmada-io/karmada (Go): affected all versions; fixed in 1.8.0 - github.com/karmada-io/karmada (Go): affected all versions; fixed in 1.8.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/GHSA-7xg2-83f8-39mr/ (Markdown: https://insights.sbomify.com/GHSA-7xg2-83f8-39mr/index.md) ``` ## Sources - OSV: https://osv.dev/vulnerability/GHSA-7xg2-83f8-39mr --- From sbomify Insights: https://insights.sbomify.com/GHSA-7xg2-83f8-39mr/ Summaries are generated and may contain mistakes; the official description above is the record.