go.etcd.io/etcd Authentication Bypass
The etcd Project etcd:
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go.etcd.io/etcd/v3 Go |
|
|
| go.etcd.io/etcd Go |
|
The etcd Project etcd:
| Product | Affected | Fixed in |
|---|---|---|
| go.etcd.io/etcd/v3 Go |
|
|
| go.etcd.io/etcd Go |
|
0.5.0-alpha.5.0.20190108173120-83c051b701d3etcd versions 3.2.x before 3.2.26 and 3.3.x before 3.3.11 are vulnerable to an improper authentication issue when role-based access control (RBAC) is used and client-cert-auth is enabled. If an etcd client server TLS certificate contains a Common Name (CN) which matches a valid RBAC username, a remote attacker may authenticate as that user with any valid (trusted) client certificate in a REST API request to the gRPC-gateway.
From the CVE record · redhat
etcd has an authentication flaw when RBAC and client-cert-auth are enabled and a client server TLS certificate’s Common Name matches a valid RBAC username. A remote attacker with any valid, trusted client certificate may authenticate as that user through a REST API request to the gRPC-gateway.
Check etcd 3.2.x before 3.2.26 and 3.3.x before 3.3.11, go.etcd.io/etcd/v3 in the listed affected ranges, and go.etcd.io/etcd before 0.5.0-alpha.5.0.20190108173120-83c051b701d3.