Описание
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.
| Релиз | Статус | Примечание |
|---|---|---|
| bionic | ignored | end of standard support, was needed |
| devel | needed | |
| esm-apps-legacy/xenial | needed | |
| esm-apps/bionic | released | 3.2.17+dfsg-1ubuntu0.1~esm1 |
| esm-apps/focal | released | 3.2.26+dfsg-6ubuntu0.1 |
| esm-apps/jammy | needed | |
| esm-apps/noble | needed | |
| esm-apps/resolute | needed | |
| esm-apps/xenial | ignored | end of ESM support, was needed |
| esm-infra-legacy/trusty | DNE |
Показывать по
EPSS
4 Medium
CVSS2
6.5 Medium
CVSS3
Связанные уязвимости
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 ...
EPSS
4 Medium
CVSS2
6.5 Medium
CVSS3