Improper authentication in etcd
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| etcd-io | etcd | affected |
|
Configuration 1 [-]
|
Configuration 2 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat OpenShift Container Platform 4.8 | |||
| openshift4/ose-etcd:v4.8.0-202106152230.p0.git.aefa6bf.assembly.stream | cpe:/a:redhat:openshift:4.8::el8 | RHSA-2021:2438 | 2021-07-27T00:00:00Z |
| Red Hat OpenStack Platform 16.1 | |||
| etcd-0:3.3.23-1.el8ost | cpe:/a:redhat:openstack:16.1::el8 | RHSA-2021:0916 | 2021-03-17T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2024-0452 | In ectd before versions 3.4.10 and 3.3.23, gateway TLS authentication is only applied to endpoints detected in DNS SRV records. When starting a gateway, TLS authentication will only be attempted on endpoints identified in DNS SRV records for a given domain, which occurs in the discoverEndpoints function. No authentication is performed against endpoints provided in the --endpoints flag. This has been fixed in versions 3.4.10 and 3.3.23 with improved documentation and deprecation of the functionality. |
Github GHSA |
GHSA-wr2v-9rpq-c35q | Etcd Gateway TLS authentication only applies to endpoints detected in DNS SRV records |
No CVSS v4.0
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: 1.7% (1.650% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.