GHSA-7xg2-83f8-39mr

Suggest an improvement
Source
https://github.com/advisories/GHSA-7xg2-83f8-39mr
Import Source
https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2024/01/GHSA-7xg2-83f8-39mr/GHSA-7xg2-83f8-39mr.json
JSON Data
https://api.osv.dev/v1/vulns/GHSA-7xg2-83f8-39mr
Aliases
Published
2024-01-03T20:06:51Z
Modified
2024-06-28T15:58:45.337904Z
Summary
The DES/3DES cipher was used as part of the TLS protocol by installation tools
Details

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
References

Affected packages

Go / github.com/karmada-io/karmada

Package

Name
github.com/karmada-io/karmada
View open source insights on deps.dev
Purl
pkg:golang/github.com/karmada-io/karmada

Affected ranges

Type
SEMVER
Events
Introduced
0Unknown introduced version / All previous versions are affected
Fixed
1.8.0