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.
Metrics
Affected Vendors & Products
Advisories
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2023-0749 | 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. |
Github GHSA |
GHSA-p4g4-wgrh-qrg2 | Panic due to malformed WALs in go.etcd.io/etcd |
Ubuntu USN |
USN-5628-1 | etcd vulnerabilities |
Ubuntu USN |
USN-5628-2 | etcd vulnerabilities |
Fixes
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
References
History
No history.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2024-08-04T13:08:21.619Z
Reserved: 2020-06-25T00:00:00
Link: CVE-2020-15106
No data.
Status : Modified
Published: 2020-08-05T19:15:10.903
Modified: 2024-11-21T05:04:49.420
Link: CVE-2020-15106
OpenCVE Enrichment
No data.
EUVD
Github GHSA
Ubuntu USN