Skip to content
Fencer Intel
low —

GHSA-vjg6-93fv-qv64 json

Etcd auth Inaccurate logging of authentication attempts for users with CN-based auth only

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

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

### Vulnerability type Logging

### Detail etcd users who have no password can authenticate only through a client certificate. When such users try to authenticate into etcd using the Authenticate endpoint, errors are logged with insufficient information regarding why the authentication failed, and may be misleading when auditing etcd 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-vjg6-93fv-qv64 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.