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.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Centos_linux | — | Upgrade etcdUpgrade etcd-debuginfo | Aug 28, 2019 | Jan 14, 2019 |
| Debian | — | Upgrade etcd | Jul 30, 2024 | Jan 14, 2019 |
| Redhat_linux | — | Upgrade etcdUpgrade etcd-debuginfo | Feb 1, 2019 | Jan 14, 2019 |
| Ubuntu | — | No solution exists | Jun 26, 2025 | Jan 14, 2019 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Jan 20, 2025 | Jan 14, 2019 |
With curated Threat Intelligence, you can see which vulnerabilities truly put you at risk, prioritize what matters most, and act before attackers do.
Explore Intelligence Hub