Количество 9
Количество 9
CVE-2020-15106
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.
CVE-2020-15106
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.
CVE-2020-15106
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.
CVE-2020-15106
CVE-2020-15106
In etcd before versions 3.3.23 and 3.4.10, a large slice causes panic ...
GHSA-p4g4-wgrh-qrg2
Panic due to malformed WALs in go.etcd.io/etcd
openSUSE-SU-2025:0003-1
Security update for etcd
SUSE-SU-2020:3760-1
Security changes in Kubernetes, etcd, and helm; Bugfix in cri-o package
SUSE-SU-2024:3656-1
Security update for etcd
Уязвимостей на страницу
Уязвимость | CVSS | EPSS | Опубликовано | |
|---|---|---|---|---|
 | CVE-2020-15106 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. | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад |
 | CVE-2020-15106 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. | CVSS3: 6.5 | 1% Низкий | около 6 лет назад |
 | CVE-2020-15106 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. | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад |
 | CVSS3: 6.5 | 1% Низкий | больше 4 лет назад | |
| CVE-2020-15106 In etcd before versions 3.3.23 and 3.4.10, a large slice causes panic ... | CVSS3: 6.5 | 1% Низкий | почти 6 лет назад |
| GHSA-p4g4-wgrh-qrg2 Panic due to malformed WALs in go.etcd.io/etcd | CVSS3: 3.7 | 1% Низкий | больше 3 лет назад |
 | openSUSE-SU-2025:0003-1 Security update for etcd | больше 1 года назад | ||
| SUSE-SU-2020:3760-1 Security changes in Kubernetes, etcd, and helm; Bugfix in cri-o package | больше 5 лет назад | ||
| SUSE-SU-2024:3656-1 Security update for etcd | почти 2 года назад |
Уязвимостей на страницу