CVE-2020-15106
Published: 5 August 2020
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.
Priority
Status
| Package | Release | Status |
|---|---|---|
|
etcd Launchpad, Ubuntu, Debian |
bionic |
Needed
|
| focal |
Released
(3.2.26+dfsg-6ubuntu0.1)
|
|
| groovy |
Ignored
(reached end-of-life)
|
|
| hirsute |
Ignored
(reached end-of-life)
|
|
| impish |
Ignored
(reached end-of-life)
|
|
| jammy |
Needed
|
|
| kinetic |
Needed
|
|
| lunar |
Needed
|
|
| trusty |
Does not exist
|
|
| upstream |
Released
(3.3.23, 3.4.10)
|
|
| xenial |
Needed
|
|
|
Patches: upstream: https://github.com/etcd-io/etcd/pull/12638/commits/b14255c0b4d1a27221d1857ae0e72bcac7f2b146 (3.3.23) |
||
Severity score breakdown
| Parameter | Value |
|---|---|
| Base score | 6.5 |
| Attack vector | Network |
| Attack complexity | Low |
| Privileges required | Low |
| User interaction | None |
| Scope | Unchanged |
| Confidentiality | None |
| Integrity impact | None |
| Availability impact | High |
| Vector | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H |