CVE-2020-15106GO-2020-0005BIT-ETCD-2020-15106BIT-ETCD-2020-15112GHSA-M332-53R6-2W93GHSA-P4G4-WGRH-QRG2
Improper Input Validation in etcd
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 3.3.23, 3.4.10, 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
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.
Timeline
- CVE published
- Record last updated
Affected versions
- etcd-io etcd
fixed in 3.3.23; fixed in 3.4.10
- go.etcd.io/etcdGo
fixed in 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4
- go.etcd.io/etcd/v3Go
fixed in 3.3.23
- go.etcd.io/etcd/v3Go
From 3.4.0 · fixed in 3.4.10