Descriptionetcd 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.
Overall state of this security issue: Resolved
This issue is currently rated as having moderate severity.
- SUSE-SU-2019:0330-1, published Tue Feb 12 04:10:29 MST 2019
List of released packages
|Product(s)||Fixed package version(s)||References|
|SUSE CaaS Platform 3.0|| ||Patchnames:
Status of this issue by product and package
Please note that this evaluation state might be work in progress, incomplete or outdated. Also information for service packs in the LTSS phase is only included for issues meeting the LTSS criteria. If in doubt, feel free to contact us for clarification.
|CaaS Platform 1.0||etcd||Not affected|
|CaaS Platform 2.0||etcd||Not affected|
|CaaS Platform 3.0||etcd||Released|
|OpenStack Cloud Magnum Orchestration 7.0||etcd||Not affected|