Skip to content

go.etcd.io/etcd Authentication Bypass

High severity GitHub Reviewed Published Apr 12, 2022 to the GitHub Advisory Database • Updated Aug 30, 2023

Package

gomod go.etcd.io/etcd (Go)

Affected versions

< 0.5.0-alpha.5.0.20190108173120-83c051b701d3

Patched versions

0.5.0-alpha.5.0.20190108173120-83c051b701d3
gomod go.etcd.io/etcd/v3 (Go)
>= 3.2.0, < 3.2.26
>= 3.3.0, < 3.3.11
3.2.26
3.3.11

Description

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.

References

Reviewed May 19, 2021
Published to the GitHub Advisory Database Apr 12, 2022
Last updated Aug 30, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(72nd percentile)

Weaknesses

CVE ID

CVE-2018-16886

GHSA ID

GHSA-h6xx-pmxh-3wgp

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.