You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
CVE-2020-15106 - Medium Severity Vulnerability
Vulnerable Libraries - github.com/etcd-io/etcd-v3.1.20, github.com/etcd-io/etcd/wal-v3.1.20
github.com/etcd-io/etcd-v3.1.20
Distributed reliable key-value store for the most critical data of a distributed system
Dependency Hierarchy:
github.com/etcd-io/etcd/wal-v3.1.20
Distributed reliable key-value store for the most critical data of a distributed system
Dependency Hierarchy:
Found in HEAD commit: 549c2321b216d811654d8e364e811dbca812a5a6
Found in base branch: master
Vulnerability 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.
Publish Date: 2020-08-05
URL: CVE-2020-15106
CVSS 3 Score Details (6.5)
Base Score Metrics:
Suggested Fix
Type: Upgrade version
Origin: etcd-io/etcd@v3.4.9...v3.4.10
Release Date: 2020-07-21
Fix Resolution: 3.4.10, 3.3.23
The text was updated successfully, but these errors were encountered: