ALT-PU-2020-2736: package etcd update to version 3.4.13-alt1
Описание
This update upgrades etcd to version 3.4.13-alt1.
Устраненные уязвимости6
Ссылки7
GHSA-2xhq-gv6c-p224
https://github.com/advisories/GHSA-2xhq-gv6c-p224GHSA-4993-m7g5-r9hh
https://github.com/advisories/GHSA-4993-m7g5-r9hhGHSA-chh6-ppwq-jh92
https://github.com/advisories/GHSA-chh6-ppwq-jh92GHSA-m332-53r6-2w93
https://github.com/advisories/GHSA-m332-53r6-2w93GHSA-p4g4-wgrh-qrg2
https://github.com/advisories/GHSA-p4g4-wgrh-qrg2GHSA-wr2v-9rpq-c35q
https://github.com/advisories/GHSA-wr2v-9rpq-c35qСвязанные уязвимости
Security changes in Kubernetes, etcd, and helm; Bugfix in cri-o package
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.
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.
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.
