Approved changes feed: RSS · Atom
cpe:2.3:a:the_etcd_project:etcd::*:*:*:*:*:*:*:*part: a version: * update: *
| Vendor | The Etcd Project (88d6e518-d3bb-5683-9db0-06387f139b60) |
|---|---|
| Product | Etcd (f932f2b9-d9a6-57fc-9e23-75050039189e) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
Notes
Imported from gcve-enriched-dumps CVE data
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2018-16886 |
vulnerable | 2026-06-08 05:11:05.730546 |
Details available
MEDIUM (6.8)
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.
Published: 2019-01-14T19:00:00.000Z
Updated: 2024-08-05T10:32:54.152Z Reference links
|
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.
Inspect record JSON
Open this panel to browse, search, copy or download the JSON record.