DEBIAN-CVE-2020-15106
Record from OSV · Published August 5, 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.
Fixed versions
Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.
| Package | Ecosystem | Fixed in |
|---|---|---|
| etcd | Debian:12 | 3.3.25+dfsg-5 |
| etcd | Debian:13 | 3.3.25+dfsg-5 |
| etcd | Debian:14 | 3.3.25+dfsg-5 |
Risk scores
Affected products
| Vendor | Product | Versions |
|---|---|---|
| Debian:12 | etcd | 0 |
| Debian:13 | etcd | 0 |
| Debian:14 | etcd | 0 |
Timeline
- Aug 5, 2020 CVE Published
- Oct 26, 2026 CVE Updated
Query this with the API
The same record, from the CLI:
vulnetix vdb vuln DEBIAN-CVE-2020-15106
vulnetix vdb fixes DEBIAN-CVE-2020-15106
Or with curl, using the org id and key from your account page:
curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
"https://api.vdb.vulnetix.com/v2/vuln/DEBIAN-CVE-2020-15106/fixes/registry"
The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart