GHSA-j86v-2vjr-fg8f json
Etcd Gateway TLS endpoint validation only confirms TCP reachability
published 2y ago modified 2mo ago also GO-2024-2528
- 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
### Workarounds Refer to the [gateway documentation](https://github.com/etcd-io/etcd/blob/master/Documentation/op-guide/gateway.md). The vulnerability was spotted due to unclear documentation of how the gateway handles endpoints validation.
### Detail Secure endpoint validation is performed by the etcd gateway start command when the --discovery-srv flag is enabled. However, as currently implemented, it only validates TCP reachability, effectively allowing connections to an endpoint that doesn't accept TLS connections through the HTTPS URL. The auditors has noted that appropriate documentation of this validation functionality plus deprecation of this misleading functionality is an acceptable path forward.
### 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/v3 3.3.23, 3.4.10
Is GHSA-j86v-2vjr-fg8f 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/v3 | >=3.4.0-rc.0, <3.4.10 <3.3.23 all versions |
3.4.10 3.3.23 |
| go | go.etcd.io/etcd | all versions |
no fix listed |
References
Sources
- GitHub Advisory GHSA-j86v-2vjr-fg8f
- OSV GO-2024-2528
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.