Improper Input Validation in etcd
etcd-io etcd
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| go.etcd.io/etcd/v3 Go |
|
|
| go.etcd.io/etcd Go |
|
|
etcd-io etcd
| Product | Affected | Fixed in |
|---|---|---|
| go.etcd.io/etcd/v3 Go |
|
|
| go.etcd.io/etcd Go |
|
|
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.
From the CVE record · GitHub_M
etcd does not validate the record length stored in a WAL file before decoding it. An attacker who can forge an extremely large frame size in that file can cause a RAFT participant to panic when it decodes the WAL. The input does not specify whether this requires network or local access, authentication, or user interaction.
Engineers running etcd before 3.3.23 or versions 3.4.0 through 3.4.9, or using affected go.etcd.io/etcd/v3 or go.etcd.io/etcd packages, should check their deployments.