GHSA-9gp7-6833-wv89 json
etcd having a negative value for cluster node size results in an index out-of-bound panic during service discovery
published 4y ago modified 4y ago
- 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 Data Validation
### Detail When an etcd instance attempts to perform service discovery, if a cluster size is provided as a negative value, the etcd instance will panic without recovery.
### References Find out more on this vulnerability in the [security audit report](https://github.com/etcd-io/etcd/blob/master/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/master/security/security-release-process.md#product-security-committee-psc)
Patch / fix
- go go.etcd.io/etcd/client/v3 3.3.23, 3.4.10
Is GHSA-9gp7-6833-wv89 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 FencerAffected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | go.etcd.io/etcd/client/v3 | >=3.4.0, <3.4.10 <3.3.23 |
3.4.10 3.3.23 |
References
Sources
- GitHub Advisory GHSA-9gp7-6833-wv89
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.