Skip to content

← Public intelligence

Go package

github.com/etcd-io/etcd

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

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

  1. Medium, CVSS 5.7GoPublished

    Improper Preservation of Permissions in etcd

    CVE-2020-15113 · GHSA-chh6-ppwq-jh92

    Affected
    • Go github.com/etcd-io/etcd >= 3.4.0-rc.0, < 3.4.10; < 3.3.23
    Fixed in
    3.3.233.4.10· Vendor fix available
    Issue
    Vulnerability type Access Controls Detail etcd creates certain directory paths (etcd data directory and the directory path when provided to automatically generate self-signed certificates for TLS connections with clients) with restricted access permissions (700) by using the os.MkdirAll. This function does not perform any permission checks when a given directory path exists already. Specific Go Package Affected github.com/etcd-io/etcd/pkg/fileutil Workarounds Make sure these directories have the desired permit (700). 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. Low, CVSS 3.1GoPublished

    etcd Key name can be accessed via LeaseTimeToLive API

    CVE-2023-32082 · GHSA-3p4g-rcw5-8298

    Affected
    • Go github.com/etcd-io/etcd < 3.4.26; >= 3.5.0, < 3.5.9
    Fixed in
    3.5.93.4.26· Vendor fix available
    Issue
    Impact LeaseTimeToLive API allows access to key names (not value) associated to a lease when Keys parameter is true, even a user doesn't have read permission to the keys. The impact is limited to a cluster which enables auth (RBAC). Patches < v3.4.26 and < v3.5.9 are affected. Workarounds No. Reporter Yoni Rozenshein

    Recommended action: Upgrade to 3.5.9 or 3.4.26 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 →