CVE-2020-15106: In etcd before versions 3.3.23 and 3.4.10, a large slice causes panic in decodeRecord method.
Medium CVSS 6.5
- CVE id
- CVE-2020-15106
- Published
- Last modified
Affected packages
| Package | Affected versions | Fixed in |
|---|---|---|
| etcd Runtimes and servers |
< 3.3.23 >= 3.4.0, < 3.4.10 |
3.3.23, 3.4.10 |
How to fix it
Upgrade etcd to the fixed release of the line you run: 3.3.23, 3.4.10.
etcd --version
- Upgrade etcd (the etcd image tag) to the patched release, member by member.
A free AIssue account reads the runtime versions your repositories pin (version files, Dockerfiles, build files) and tells you when one is affected.
Details
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.
References
- CVE-2020-15106 on the NVD
- Advisory: https://nvd.nist.gov/vuln/detail/CVE-2020-15106
- Web: https://github.com/etcd-io/etcd/security/advisories/GHSA-p4g4-wgrh-qrg2
- Web: https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L6B6R43Y7M3DCHWK3L3UVGE2K6WWECMP/
- Web: https://github.com/etcd-io/etcd/security/advisories/GHSA-p4g4-wgrh-qrg2
- Web: https://lists.fedoraproject.org/archives/list/package-announce%40lists.fedoraproject.org/message/L6B6R43Y7M3DCHWK3L3UVGE2K6WWECMP/
Am I affected?
Upload or paste your lockfile. We check every package version in it against OSV.dev, this advisory included, and email you the vulnerable ones with the version that fixes them. Free, and no account needed.
About this data
Source: National Vulnerability Database (NVD) (public domain). Severity comes from the advisory's own rating when it has one, else from its CVSS score.