go.etcd.io/etcd Authentication Bypass
etcd 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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2018-16886US | high8.1 | — | ||
etcd 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 e… | ||||
02
references
External citations — patches, advisories, analysis.
- http://www.securityfocus.com/bid/106540WEB
- https://access.redhat.com/errata/RHSA-2019:0237WEB
- https://access.redhat.com/errata/RHSA-2019:1352WEB
- https://bugzilla.redhat.com/show_bug.cgi?id=CVE-2018-16886WEB
- https://github.com/etcd-io/etcdPACKAGE
- https://github.com/etcd-io/etcd/blob/1eee465a43720d713bb69f7b7f5e120135fdb1ac/CHANGELOG-3.2.md#security-authenticationWEB
- https://github.com/etcd-io/etcd/blob/1eee465a43720d713bb69f7b7f5e120135fdb1ac/CHANGELOG-3.3.md#security-authenticationWEB
- https://github.com/etcd-io/etcd/commit/0191509637546621d6f2e18e074e955ab8ef374dWEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan