Skip to content

← Public intelligence

Go package

go.etcd.io/etcd/client/v3

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. UnratedGoPublished

    etcd having a negative value for cluster node size results in an index out-of-bound panic during service discovery

    GHSA-9gp7-6833-wv89

    Affected
    • Go go.etcd.io/etcd/client/v3 >= 3.4.0, < 3.4.10; < 3.3.23
    Fixed in
    3.3.233.4.10· Vendor fix available
    Issue
    Vulnerability type Data Validation Detail When an etcd instance attempts to perform service discovery, if a cluster size is provided as a negative value, the etcd instance will panic without recovery. References Find out more on this vulnerability in the security audit report For more information If you have any questions or comments about this advisory: Contact the etcd security committee

    Recommended action: Upgrade to 3.4.10 or 3.3.23 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. UnratedGoPublished

    etcd user credentials are stored in WAL logs in plaintext

    GHSA-528j-9r78-wffx

    Affected
    • Go go.etcd.io/etcd/client/v3 >= 3.4.0, < 3.4.10; < 3.3.23
    Fixed in
    3.3.233.4.10· Vendor fix available
    Issue
    Vulnerability type Data Exposure Workarounds The etcd assumes that the on disk files are secure. The possible fixes have been provided, however, it is the responsibility of the etcd users to make sure that the etcd server WAL log files are secure. The etcd doesn't encrypt key/value data stored on disk drives. Detail User credentials (login and password) are stored in WAL entries on each user authentication. If the WAL log files are not secure, it can potentially expose sensitive information. References Find out more on this vulnerability in the security audit report For more information If you have any questions or comments about this advisory: Contact the etcd security committee

    Recommended action: Upgrade to 3.4.10 or 3.3.23 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Medium, CVSS 5.8GoPublished

    etcd has no minimum password length

    CVE-2020-15115 · GHSA-4993-m7g5-r9hh

    Affected
    • Go go.etcd.io/etcd/client/v3 >= 3.4.0, < 3.4.10; < 3.3.23
    Fixed in
    3.3.233.4.10· Vendor fix available
    Issue
    Vulnerability type Access Control Workarounds The etcdctl and etcd API do not enforce a specific password length during user creation or user password update operations. It is the responsibility of the administrator to enforce these requirements. Detail etcd does not perform any password length validation, which allows for very short passwords, such as those with a length of one. This may allow an attacker to guess or brute-force users’ passwords with little computational effort. References Find out more on this vulnerability in the security audit report For more information If you have any questions or comments about this advisory: Contact the etcd security committee

    Recommended action: Upgrade to 3.4.10 or 3.3.23 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →