GHSA-7xg2-83f8-39mr: Github.com/karmada io/karmada The DES/3DES Cipher Was Used Vulnerability

LOW
Published
Advisory Summary

GHSA-7xg2-83f8-39mr is a LOW the des/3des cipher was used vulnerability (General Security Weakness) affecting Github.com/karmada io/karmada libraries in the Go ecosystem. The issue involves the des/3des cipher was used as part of the tls protocol by installation tools. Remediation is available by upgrading affected packages to version 1.8.0.

GHSA-7xg2-83f8-39mr at a Glance

CVE Identifier N/A
GHSA Identifier GHSA-7xg2-83f8-39mr
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification General Security Weakness
Affected Product Github.com/karmada io/karmada
Package Ecosystem Go
Published Date
Last Updated

How to Fix GHSA-7xg2-83f8-39mr

To remediate this vulnerability, upgrade all affected Github.com/karmada io/karmada dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/karmada-io/karmada fixed: 1.8.0
Upgrade github.com/karmada-io/karmada to 1.8.0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/karmada-io/karmada

How to Check if You Are Affected

To determine whether your application is affected by GHSA-7xg2-83f8-39mr, inspect your project dependencies for Github.com/karmada io/karmada:

inspect dependencies for github.com/karmada-io/karmada

Analyze the terminal output to locate any version of Github.com/karmada io/karmada in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.8.0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under General Security Weakness. In Github.com/karmada io/karmada, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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

GHSA-7xg2-83f8-39mr Affected Github.com/karmada io/karmada Versions

1 component(s)
Fixed Versions:
1.8.0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/karmada-io/karmada
Go
< 1.8.0
1.8.0

References

Frequently Asked Questions

What is GHSA-7xg2-83f8-39mr?
GHSA-7xg2-83f8-39mr is a security vulnerability in Github.com/karmada io/karmada involving The DES/3DES cipher was used as part of the TLS protocol by installation tools under General Security Weakness.
Which Github.com/karmada io/karmada versions are affected?
Affected versions include releases prior to 1.8.0 across affected packages: github.com/karmada-io/karmada.
What version fixes GHSA-7xg2-83f8-39mr?
Upgrading to 1.8.0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/karmada-io/karmada affected?
Yes, github.com/karmada-io/karmada is affected in releases prior to 1.8.0. Upgrade your dependency to 1.8.0 or later.
What CWE is associated with GHSA-7xg2-83f8-39mr?
GHSA-7xg2-83f8-39mr is classified under General Security Weakness.
How can I check Go dependencies for GHSA-7xg2-83f8-39mr?
Run the dependency tree command: 'inspect dependencies for github.com/karmada-io/karmada'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7xg2-83f8-39mr",
  "modified" : "2024-01-03T20:06:51Z",
  "published" : "2024-01-03T20:06:51Z",
  "aliases" : [ ],
  "summary" : "The DES/3DES cipher was used as part of the TLS protocol by installation tools",
  "details" : "### Impact\n_What kind of vulnerability is it? Who is impacted?_\n\nThe 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.\n\nThe components affected are:\n- karmada-apiserver\n- karmada-aggregated-apiserver\n- karmada-search\n- karmada-metrics-adapter\n- etcd\n\n### Patches\n_Has the problem been patched? What versions should users upgrade to?_\n\nFrom 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`.\n\n### Workarounds\n_Is there a way for users to fix or remediate the vulnerability without upgrading?_\n\nBy setting the `--tls-min-version` for the affected components to TLS 1.3, or explicitly setting the `--cipher-suites` to secure algorithms.\n\n### References\n_Are there any links users can visit to find out more?_\n\n1. Enhancements made from the Karmada community: https://github.com/karmada-io/karmada/issues/4191\n2. Impact discussions from the Golang community: https://github.com/golang/go/issues/41476",
  "severity" : [ ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/karmada-io/karmada"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.8.0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/karmada-io/karmada/security/advisories/GHSA-7xg2-83f8-39mr"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/golang/go/issues/41476"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/karmada-io/karmada/issues/4191"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/karmada-io/karmada/commit/98e655fc552b2987c3f2d2a061007889ce8be536"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/karmada-io/karmada/commit/c3c376605403e07ca0ed2dc39c9e0f3c38f8e29d"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/karmada-io/karmada"
  } ],
  "database_specific" : {
    "cwe_ids" : [ ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2024-01-03T20:06:51Z",
    "nvd_published_at" : null
  }
}