In etcd before versions 3.3.23 and 3.4.10, a large slice causes panic in decodeRecord method. The size of a record is stored in the length field of a WAL file and no additional validation is done on this data. Therefore, it is possible to forge an extremely large frame size that can unintentionally panic at the expense of any RAFT participant trying to decode the WAL.
| Product | Vendor Advisory | Solution File | Added | Published |
|---|---|---|---|---|
| Centos_linux | — | Upgrade etcd-debuginfoUpgrade etcd | Jun 1, 2021 | Aug 5, 2020 |
| Debian | — | Upgrade etcd | Jul 30, 2024 | Aug 5, 2020 |
| Redhat_linux | — | Upgrade etcd-debuginfoUpgrade etcd | Apr 28, 2021 | Aug 5, 2020 |
| Suse | — | Upgrade kubernetes-clientUpgrade kubernetes-common | Feb 4, 2022 | Aug 5, 2020 |
| Ubuntu | — | Upgrade etcd-client (Ubuntu Pro)Upgrade etcd-serverUpgrade etcd-server (Ubuntu Pro)Upgrade etcd-clientUpgrade etcdUpgrade etcd (Ubuntu Pro) | Sep 23, 2022 | Aug 5, 2020 |
| Vmware Photon_os | — | Use 'tdnf update' to upgrade all packages to the latest version. | Jan 20, 2025 | Aug 5, 2020 |
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