Skip to content
Fencer Intel
low —

GHSA-pm3m-32r3-7mfh json

Etcd embed auto compaction retention negative value causing a compaction loop or a crash

published 2y ago modified 2mo ago also GO-2024-2529

cvss
—
not scored
cisa kev
Not listed
not in CISA's catalog
epss
—
no score, EPSS covers CVEs only
public exploits
0
none known

Summary

### Impact Data Validation

### Detail The parseCompactionRetention function in embed/etcd.go allows the retention variable value to be negative and causes the node to execute the history compaction in a loop, taking more CPU than usual and spamming logs.

### 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)

Patch / fix

  • go go.etcd.io/etcd/v3 3.3.23, 3.4.10

Is GHSA-pm3m-32r3-7mfh in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Affected packages

ecosystem package affected fixed in
go go.etcd.io/etcd/v3
>=3.4.0-rc.0, <3.4.10
<3.3.23
all versions
3.4.10
3.3.23
go go.etcd.io/etcd
all versions
 no fix listed

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.