CVE-2020-15106

Improper Input Validation in etcd

MEDIUM
6.5
CVSS Score
Published: August 5, 2020 at 07:05 PM UTC
Updated: June 17, 2026 at 02:56 AM UTC
3 products affected across 3 vendorsFedoraEtcd:Etcd

Using etcd by etcd-io?

Get instant alerts when new vulnerabilities affect etcd - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM6.5
Exploit prediction
EPSS 1%

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 3.3.233.4.0 ≤ v < 3.4.10
Affected range stops below 3.3.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.10, so it looks safe — our inference, not a vendor statement
v < 3.3.23v < 3.4.10
Affected range stops below 3.3.23, so it looks safe — our inference, not a vendor statement
Affected range stops below 3.4.10, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

CVSS

6.5MEDIUMGitHub_M
Attack Vector
NETWORK
Complexity
LOW
Privileges
LOW
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-20NVD-CWE-Other

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card