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

etcd: · Vulnerability

CVSS 3.0 6.8 MEDIUMEUVD CVSS 3.0 6.8 CVSS 3.1 · [email protected] · Primary 8.1 HIGHCVSS 3.0 · [email protected] · Secondary 6.8 MEDIUMCVSS 2.0 · [email protected] · Primary 6.8 MEDIUMCVSS_V3 Publisher rating HIGHFixed by go.etcd.io/etcd/v3 3.2.26Fixed by go.etcd.io/etcd/v3 3.3.11Fixed by go.etcd.io/etcd 0.5.0-alpha.5.0.20190108173120-83c051b701d3osv · severity unknownFixed by go.etcd.io/etcd 0.5.0-alpha.5.0.20190108173120-83c051b701d3KEV status unknown

cve-program · CVE-2018-16886

Published

etcd versions 3.2.x before 3.2.26 and 3.3.x before 3.3.11 are vulnerable to an improper authentication issue when role-based access control (RBAC) is used and client-cert-auth is enabled. If an etcd client server TLS certificate contains a Common Name (CN) which matches a valid RBAC username, a remote attacker may authenticate as that user with any valid (trusted) client certificate in a REST API request to the gRPC-gateway.

Read the publisher's advisory

euvd · EUVD-2022-1756

Published

etcd versions 3.2.x before 3.2.26 and 3.3.x before 3.3.11 are vulnerable to an improper authentication issue when role-based access control (RBAC) is used and client-cert-auth is enabled. If an etcd client server TLS certificate contains a Common Name (CN) which matches a valid RBAC username, a remote attacker may authenticate as that user with any valid (trusted) client certificate in a REST API request to the gRPC-gateway.

Read the publisher's advisory

nvd · CVE-2018-16886

Published

etcd versions 3.2.x before 3.2.26 and 3.3.x before 3.3.11 are vulnerable to an improper authentication issue when role-based access control (RBAC) is used and client-cert-auth is enabled. If an etcd client server TLS certificate contains a Common Name (CN) which matches a valid RBAC username, a remote attacker may authenticate as that user with any valid (trusted) client certificate in a REST API request to the gRPC-gateway.

Read the publisher's advisory

osv · GHSA-h6xx-pmxh-3wgp

Published

etcd versions 3.2.x before 3.2.26 and 3.3.x before 3.3.11 are vulnerable to an improper authentication issue when role-based access control (RBAC) is used and client-cert-auth is enabled. If an etcd client server TLS certificate contains a Common Name (CN) which matches a valid RBAC username, a remote attacker may authenticate as that user with any valid (trusted) client certificate in a REST API request to the gRPC-gateway.

Read the publisher's advisory

osv · GO-2021-0077

Published

A user can use a valid client certificate that contains a CommonName that matches a valid RBAC username to authenticate themselves as that user, despite lacking the required credentials. This may allow authentication bypass, but requires a certificate that is issued by a CA trusted by the server.

Read the publisher's advisory

Affected versions, risk and source history

Related advisories and sources

Publishers link these advisories through the identifiers shown below. A shared identifier or date alone does not tell you whether your software is affected or whether the advisories describe the same cause.

CVE-2018-16886 · CVE overview and exploitation status

EUVD-2022-1756

GHSA-h6xx-pmxh-3wgp

GO-2021-0077

cve-program · CVE-2018-16886

euvd · EUVD-2022-1756

nvd · CVE-2018-16886

osv · GHSA-h6xx-pmxh-3wgp

osv · GO-2021-0077

Related changes

Linked by CVE identifier

No related changes are available here.

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 19 Nov 04:49 UTC · 273 of 275 readable · 269 fully read · documentation 469/469 current