Public mode

No access to your tenant or devices. Every item links to its source. What this means

Sources need attention Customize Public modeDiscuss ChangeIntel on Discord

Improper Input Validation in etcd

CVSS 3.1 6.5 MEDIUMCVSS 3.1 6.5 MEDIUMEUVD CVSS 3.1 6.5 EUVD CVSS 3.1 6.5 CVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS 3.1 · [email protected] · Primary 6.5 MEDIUMCVSS 2.0 · [email protected] · Primary 4.0 MEDIUMCVSS 3.1 · [email protected] · Secondary 6.5 MEDIUMCVSS 3.1 · [email protected] · Primary 6.5 MEDIUMCVSS 2.0 · [email protected] · Primary 4.0 MEDIUMCVSS_V3 Publisher rating MODERATEFixed by go.etcd.io/etcd/v3 3.3.23Fixed by go.etcd.io/etcd/v3 3.4.10CVSS_V3 Publisher rating LOWFixed by go.etcd.io/etcd 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4osv · severity unknownFixed by go.etcd.io/etcd 0.5.0-alpha.5.0.20200423152442-f4b650b51dc4KEV status unknown

cve-program · CVE-2020-15106

Published

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.

Read the publisher's advisory

cve-program · CVE-2020-15112

Published

In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry.

Read the publisher's advisory

euvd · EUVD-2022-7121

Published

In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry.

Read the publisher's advisory

euvd · EUVD-2023-0749

Published

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.

Read the publisher's advisory

nvd · CVE-2020-15106

Published

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.

Read the publisher's advisory

nvd · CVE-2020-15112

Published

In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry.

Read the publisher's advisory

osv · GHSA-m332-53r6-2w93

Published

### Vulnerability type Data Validation ### Detail In the ReadAll method in wal/wal.go, it is possible to have an entry index greater then the number of entries. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry. ### References Find out more on this vulnerability in the [security audit report](https://github.com/etcd-io/etcd/blob/master/security/SECURITY_AUDIT.pdf) ### For more information If you have any questions or comments about this advisory: * Contact the [etcd security committee](https://github.com/etcd-io/etcd/blob/master/security/security-release-process.md)

Read the publisher's advisory

osv · GHSA-p4g4-wgrh-qrg2

Published

### Vulnerability type Data Validation ### Detail 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. ### Specific Go Packages Affected github.com/etcd-io/etcd/wal ### References Find out more on this vulnerability in the [security audit report](https://github.com/etcd-io/etcd/blob/master/security/SECURITY_AUDIT.pdf) ### For more information If you have any questions or comments about this advisory: * Contact the [etcd security committee](https://github.com/etcd-io/etcd/blob/master/security/security-release-process.md#product-security-committee-psc)

Read the publisher's advisory

osv · GO-2020-0005

Published

Malformed WALs can be constructed such that WAL.ReadAll can cause attempted out of bounds reads, or creation of arbitrarily sized slices, which may be used as a DoS vector.

Read the publisher's advisory

Affected versions, risk and source history

Exploitation and risk

Source status

CISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.

Which CVEs have scores here?

This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.

No exploitation or prediction data is available here for these CVEs. This does not mean they are safe or unlikely to be exploited.

cve-program · CVE-2020-15106

Published

Improper Input Validation in etcd

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.

Source published
5 Aug 2020 19:05:13 UTC
Source modified
4 Aug 2024 13:08:21 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

cve-program · CVE-2020-15112

Published

Improper Input Validation in etcd

In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry.

Source published
5 Aug 2020 20:00:15 UTC
Source modified
4 Aug 2024 13:08:22 UTC
Saved here
23 Oct 2026 15:48:27 UTC
Source terms
CVE Program Terms of Use

Original source record · Cite this exact observation · Complete original publisher JSON

Source: cve-program · CVE Program Terms of Use. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

euvd · EUVD-2022-7121

Published

In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrar…

In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 5, 2020, 8:00:15 PM

dateUpdated: Aug 4, 2024, 1:08:22 PM

6 related source bulletins · separate from aliases

SUSE-SU-2024:3656-1: Security update for etcd

CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-16886 · CVE-2020-15106 · CVE-2020-15112 · CVE-2021-28235 · CVE-2022-41723 · CVE-2023-29406 · CVE-2023-47108 · CVE-2023-48795

RHSA-2021:2438: Red Hat Security Advisory: OpenShift Container Platform 4.8.2 bug fix and security update

CVE-2016-2183 · CVE-2020-7774 · CVE-2020-15106 · CVE-2020-15112 · CVE-2020-15113 · CVE-2020-15114 · CVE-2020-15136 · CVE-2020-26160 · CVE-2020-28469 · CVE-2020-28500 · CVE-2020-28852 · CVE-2021-3114 · CVE-2021-3121 · CVE-2021-20206 · CVE-2021-20218 · CVE-2021-20291 · CVE-2021-22133 · CVE-2021-23337 · CVE-2021-23362 · CVE-2021-23368 · CVE-2021-23382 · CVE-2021-26539 · CVE-2021-26540 · CVE-2021-27292 · CVE-2021-28092 · CVE-2021-29059 · CVE-2021-29622 · CVE-2021-33194

RHSA-2021:0916: Red Hat Security Advisory: Red Hat OpenStack Platform 16.1.4 (etcd) security update

CVE-2020-15106 · CVE-2020-15112 · CVE-2020-15113 · CVE-2020-15114 · CVE-2020-15115 · CVE-2020-15136

SUSE-SU-2020:3760-1: Security changes in Kubernetes, etcd, and helm; Bugfix in cri-o package

CVE-2020-15106 · CVE-2020-15112 · CVE-2020-15184 · CVE-2020-15185 · CVE-2020-15186 · CVE-2020-15187 · CVE-2020-8565 · CVE-2020-8566

RHSA-2021:1407: Red Hat Security Advisory: etcd security update

CVE-2020-15106 · CVE-2020-15112

msrc_CVE-2020-15112: Improper Input Validation in etcd

CVE-2020-15112

Source published
Aug 5, 2020, 8:00:15 PM (timezone not stated)
Source modified
Aug 4, 2024, 1:08:22 PM (timezone not stated)
Saved here
15 Nov 2026 22:08:49 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

euvd · EUVD-2023-0749

Published

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 f…

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.

Additional publisher context

EUVD source date text has no stated timezone and is retained without inventing a UTC instant. Related bulletin membership is not an alias, common cause or applicability claim. A missing vector with a zero score is treated as unrated. Complete vendor/product and underlying source evidence remains in the original JSON.

Original publisher date fields

datePublished: Aug 5, 2020, 7:05:13 PM

dateUpdated: Aug 4, 2024, 1:08:21 PM

8 related source bulletins · separate from aliases

openSUSE-SU-2024:10741-1: etcd-3.4.16-3.1 on GA media

CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-16886 · CVE-2020-15106

RHSA-2021:1407: Red Hat Security Advisory: etcd security update

CVE-2020-15106 · CVE-2020-15112

SUSE-SU-2024:3656-1: Security update for etcd

CVE-2018-16873 · CVE-2018-16874 · CVE-2018-16875 · CVE-2018-16886 · CVE-2020-15106 · CVE-2020-15112 · CVE-2021-28235 · CVE-2022-41723 · CVE-2023-29406 · CVE-2023-47108 · CVE-2023-48795

SUSE-SU-2020:3760-1: Security changes in Kubernetes, etcd, and helm; Bugfix in cri-o package

CVE-2020-15106 · CVE-2020-15112 · CVE-2020-15184 · CVE-2020-15185 · CVE-2020-15186 · CVE-2020-15187 · CVE-2020-8565 · CVE-2020-8566

openSUSE-SU-2025:0003-1: Security update for etcd

CVE-2019-11254 · CVE-2020-15106 · CVE-2021-28235 · CVE-2023-47108 · CVE-2023-48795

RHSA-2021:0916: Red Hat Security Advisory: Red Hat OpenStack Platform 16.1.4 (etcd) security update

CVE-2020-15106 · CVE-2020-15112 · CVE-2020-15113 · CVE-2020-15114 · CVE-2020-15115 · CVE-2020-15136

msrc_CVE-2020-15106: Improper Input Validation in etcd

CVE-2020-15106

RHSA-2021:2438: Red Hat Security Advisory: OpenShift Container Platform 4.8.2 bug fix and security update

CVE-2016-2183 · CVE-2020-7774 · CVE-2020-15106 · CVE-2020-15112 · CVE-2020-15113 · CVE-2020-15114 · CVE-2020-15136 · CVE-2020-26160 · CVE-2020-28469 · CVE-2020-28500 · CVE-2020-28852 · CVE-2021-3114 · CVE-2021-3121 · CVE-2021-20206 · CVE-2021-20218 · CVE-2021-20291 · CVE-2021-22133 · CVE-2021-23337 · CVE-2021-23362 · CVE-2021-23368 · CVE-2021-23382 · CVE-2021-26539 · CVE-2021-26540 · CVE-2021-27292 · CVE-2021-28092 · CVE-2021-29059 · CVE-2021-29622 · CVE-2021-33194

Source published
Aug 5, 2020, 7:05:13 PM (timezone not stated)
Source modified
Aug 4, 2024, 1:08:21 PM (timezone not stated)
Saved here
15 Nov 2026 22:08:47 UTC
Source terms
ENISA EUVD · source terms and attribution apply

Original source record · Cite this exact observation · Complete original publisher JSON

Source: euvd · ENISA EUVD · source terms and attribution apply. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

EUVD CVSS 3.1 · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

nvd · CVE-2020-15106

Published

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 f…

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.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-20 · NVD-CWE-Other

Original publisher date fields

published: 2020-08-05T19:15:10.903

lastModified: 2026-06-17T02:56:03.950

2 source CPE criteria · context only
  • cpe:2.3:a:etcd:etcd:*:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:32:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
5 Aug 2020 19:15:10 UTC
Source modified
17 Jun 2026 02:56:03 UTC
Saved here
24 Oct 2026 16:17:20 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS 3.1 · [email protected] · Primary · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS 2.0 · [email protected] · Primary · 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P

nvd · CVE-2020-15112

Published

In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrar…

In etcd before versions 3.3.23 and 3.4.10, it is possible to have an entry index greater then the number of entries in the ReadAll method in wal/wal.go. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry.

Additional publisher context

NVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.

Source analysis status: Modified

Weakness classifications: CWE-20 · CWE-129

Original publisher date fields

published: 2020-08-05T20:15:14.553

lastModified: 2026-06-17T02:56:04.637

2 source CPE criteria · context only
  • cpe:2.3:a:etcd:etcd:*:*:*:*:*:*:*:*
  • cpe:2.3:o:fedoraproject:fedora:32:*:*:*:*:*:*:*

The original JSON retains the logical configuration operators, exclusions and version bounds.

Source published
5 Aug 2020 20:15:14 UTC
Source modified
17 Jun 2026 02:56:04 UTC
Saved here
24 Oct 2026 16:17:20 UTC
Source terms
NIST NVD usage terms; underlying source attribution retained

Original source record · Cite this exact observation · Complete original publisher JSON

Source: nvd · NIST NVD usage terms; underlying source attribution retained. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS 3.1 · [email protected] · Secondary · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS 3.1 · [email protected] · Primary · 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H

CVSS 2.0 · [email protected] · Primary · 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P

osv · GHSA-m332-53r6-2w93

Published

etcd's WAL `ReadAll` method vulnerable to an entry with large index causing panic

### Vulnerability type Data Validation ### Detail In the ReadAll method in wal/wal.go, it is possible to have an entry index greater then the number of entries. This could cause issues when WAL entries are being read during consensus as an arbitrary etcd consensus participant could go down from a runtime panic when reading the entry. ### References Find out more on this vulnerability in the [security audit report](https://github.com/etcd-io/etcd/blob/master/security/SECURITY_AUDIT.pdf) ### For more information If you have any questions or comments about this advisory: * Contact the [etcd security committee](https://github.com/etcd-io/etcd/blob/master/security/security-release-process.md)

Source published
6 Oct 2022 23:03:57 UTC
Source modified
10 Sep 2026 03:49:49 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

Publisher rating · MODERATE

osv · GHSA-p4g4-wgrh-qrg2

Published

Panic due to malformed WALs in go.etcd.io/etcd

### Vulnerability type Data Validation ### Detail 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. ### Specific Go Packages Affected github.com/etcd-io/etcd/wal ### References Find out more on this vulnerability in the [security audit report](https://github.com/etcd-io/etcd/blob/master/security/SECURITY_AUDIT.pdf) ### For more information If you have any questions or comments about this advisory: * Contact the [etcd security committee](https://github.com/etcd-io/etcd/blob/master/security/security-release-process.md#product-security-committee-psc)

Source published
7 Feb 2023 22:59:30 UTC
Source modified
10 Sep 2026 03:50:07 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
GitHub Advisory Database · CC-BY-4.0

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

CVSS_V3 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:L

Publisher rating · LOW

osv · GO-2020-0005

Published

Panic due to malformed WALs in go.etcd.io/etcd

Malformed WALs can be constructed such that WAL.ReadAll can cause attempted out of bounds reads, or creation of arbitrarily sized slices, which may be used as a DoS vector.

Source published
14 Apr 2021 20:04:52 UTC
Source modified
4 Feb 2026 03:10:38 UTC
Saved here
24 Oct 2026 13:19:41 UTC
Source terms
OSV · upstream source license applies

Original source record · Cite this exact observation · Complete original publisher JSON

Source: osv · OSV · upstream source license applies. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.

ChangeIntel

An IT change radar: releases, security, known issues, retirements, documentation changes, and service status from public sources. Every item links to supporting evidence; dates and statuses can change after they are read.

Sources read 16 Nov 17:03 UTC · 274 of 275 readable · 250 fully read · 20 waiting for GitHub's hourly limit · documentation 469/469 current