Skip to content
Fencer Intel
low —

GHSA-5x4g-q5rc-36jp json

Etcd pkg Insecure ciphers are allowed by default

published 2y ago modified 2mo ago also GO-2024-2527

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Vulnerability type Cryptography

### Detail The TLS ciphers list supported by etcd contains insecure cipher suites. Users can configure the desired ciphers using the “--cipher-suites” flag, and a default list of secure cipher suites is used if empty.

### Workarounds By default, no action is required. If users want to specify cipher suites using the '--cipher-suites' flag, they should try not to specify insecure cipher suites. Please refer to the [security documentation](https://etcd.io/docs/v3.4/op-guide/security/).

### References Find out more on this vulnerability in the [security audit report](https://github.com/etcd-io/etcd/blob/main/security/SECURITY_AUDIT.pdf)

### For more information If you have any questions or comments about this advisory: * Contact the [etcd security committee](https://github.com/etcd-io/etcd/blob/main/security/security-release-process.md#product-security-committee-psc)

Patch / fix

  • go go.etcd.io/etcd/client/pkg/v3 3.3.23, 3.4.10
  • go go.etcd.io/etcd 0.5.0-alpha.5.0.20221102000833-1f054980bc27

Is GHSA-5x4g-q5rc-36jp in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go go.etcd.io/etcd/client/pkg/v3
>=3.4.0-rc.0, <3.4.10
<3.3.23
3.4.10
3.3.23
go go.etcd.io/etcd
<0.5.0-alpha.5.0.20221102000833-1f054980bc27
0.5.0-alpha.5.0.20221102000833-1f054980bc27

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.