CVE-2020-15106

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.

How to fix CVE-2020-15106

To remediate CVE-2020-15106, upgrade the affected package to a fixed version below.

• —upgrade to 3.3.23 or later
• —upgrade to 3.3.23 or later
• —upgrade to 3.3.25+dfsg-5 or later
• —upgrade to 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4 or later
• —upgrade to 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4 or later
• —upgrade to 3.3.23 or later

Is CVE-2020-15106 being exploited?

Low — EPSS is 0.1%, meaning exploitation activity has not been observed at scale.

Affected packages (6)

• from 0, < 3.3.23, >= 3.4.0, < 3.4.10
• from 0, < 3.3.23, >= 3.4.0, < 3.4.10
• from 0, < 3.3.25+dfsg-5
• from 0, < 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4
• from 0, < 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4
• from 0, < 3.3.23

CVSS scores

References (14)

• ADVISORYnvd.nist.gov/vuln/detail/CVE-2020-15106
• ADVISORYnvd.nist.gov/vuln/detail/CVE-2020-15112
• ADVISORYsecurity-tracker.debian.org/tracker/CVE-2020-15106
• PATCHgithub.com/etcd-io/etcd
• WEB