Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

x/vulndb: potential Go vuln in github.com/cilium/cilium-cli: GHSA-6f27-3p6c-p5jc #1653

Closed
GoVulnBot opened this issue Mar 21, 2023 · 5 comments
Assignees
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.

Comments

@GoVulnBot
Copy link

In GitHub Security Advisory GHSA-6f27-3p6c-p5jc, there is a vulnerability in the following Go packages or modules:

Unit Fixed Vulnerable Ranges
github.com/cilium/cilium-cli 0.13.2 < 0.13.2

Cross references:
No existing reports found with this module or alias.

See doc/triage.md for instructions on how to triage this report.

modules:
  - module: github.com/cilium/cilium-cli
    versions:
      - fixed: 0.13.2
    packages:
      - package: github.com/cilium/cilium-cli
summary: '`cilium-cli` disables etcd authorization for clustermesh clusters'
description: "### Impact\n\n`cilium-cli`, when used to configure cluster mesh functionality,
    can remove the enforcement of user permissions on the `etcd` store used to mirror
    local cluster information to remote clusters. \n\nDue to an incorrect mount point
    specification, the settings specified by the `initContainer` that configures `etcd`
    users and their permissions are overwritten when using `cilium-cli` to configure
    a cluster mesh. An attacker who has already gained access to a valid key and certificate
    for an `etcd` cluster compromised in this manner could then modify state in that
    `etcd` cluster.\n\n### Patches\n\nThis issue is patched in `cilium-cli` 0.13.2\n\nAll
    previous versions of `cilium-cli` are affected. Users who have set up cluster
    meshes using the Cilium Helm chart are not affected.\n\n### Workarounds\n\nUse
    Cilium's [Helm charts](https://artifacthub.io/packages/helm/cilium/cilium) to
    create your cluster instead.\n\n### Acknowledgements\n\nThe Cilium community has
    worked together with members of Isovalent to prepare these mitigations. Special
    thanks to Marco Iorio for investigating and fixing the issue.\n\n### For more
    information\nIf you have any questions or comments about this advisory, please
    reach out on [Slack](https://docs.cilium.io/en/latest/community/community/#slack).\n\nAs
    usual, if you think you found a related vulnerability, we strongly encourage you
    to report security vulnerabilities to our private security mailing list: [security@cilium.io](mailto:security@cilium.io)
    - first, before disclosing them in any public forums. This is a private mailing
    list where only members of the Cilium internal security team are subscribed to,
    and is treated as top priority."
cves:
  - CVE-2023-28114
ghsas:
  - GHSA-6f27-3p6c-p5jc
references:
  - advisory: https://github.com/cilium/cilium-cli/security/advisories/GHSA-6f27-3p6c-p5jc
  - fix: https://github.com/cilium/cilium-cli/commit/fb1427025764e1eebc4a7710d902c4f22cae2610
  - web: https://github.com/cilium/cilium-cli/releases/tag/v0.13.2
  - advisory: https://github.com/advisories/GHSA-6f27-3p6c-p5jc

@julieqiu
Copy link
Member

The packages are exported but this is a tool.

@julieqiu julieqiu added the excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module. label Mar 23, 2023
@julieqiu julieqiu self-assigned this Mar 23, 2023
@gopherbot
Copy link
Contributor

Change https://go.dev/cl/478875 mentions this issue: data/excluded: batch add excluded reports

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/479297 mentions this issue: data/excluded: batch add GO-2023-1674, GO-2023-1671, GO-2023-1670, GO-2023-1669, GO-2023-1668, GO-2023-1667, GO-2023-1662, GO-2023-1661, GO-2023-1660, GO-2023-1659, GO-2023-1658, GO-2023-1657, GO-2023-1656, GO-2023-1655, GO-2023-1654, GO-2023-1653, GO-2023-1673, GO-2023-1666, GO-2023-1665

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/592760 mentions this issue: data/reports: unexclude 75 reports

@gopherbot
Copy link
Contributor

Change https://go.dev/cl/606784 mentions this issue: data/reports: unexclude 20 reports (4)

gopherbot pushed a commit that referenced this issue Aug 20, 2024
  - data/reports/GO-2023-1643.yaml
  - data/reports/GO-2023-1644.yaml
  - data/reports/GO-2023-1651.yaml
  - data/reports/GO-2023-1652.yaml
  - data/reports/GO-2023-1653.yaml
  - data/reports/GO-2023-1654.yaml
  - data/reports/GO-2023-1655.yaml
  - data/reports/GO-2023-1656.yaml
  - data/reports/GO-2023-1657.yaml
  - data/reports/GO-2023-1658.yaml
  - data/reports/GO-2023-1659.yaml
  - data/reports/GO-2023-1660.yaml
  - data/reports/GO-2023-1661.yaml
  - data/reports/GO-2023-1662.yaml
  - data/reports/GO-2023-1670.yaml
  - data/reports/GO-2023-1671.yaml
  - data/reports/GO-2023-1682.yaml
  - data/reports/GO-2023-1683.yaml
  - data/reports/GO-2023-1685.yaml
  - data/reports/GO-2023-1699.yaml

Updates #1643
Updates #1644
Updates #1651
Updates #1652
Updates #1653
Updates #1654
Updates #1655
Updates #1656
Updates #1657
Updates #1658
Updates #1659
Updates #1660
Updates #1661
Updates #1662
Updates #1670
Updates #1671
Updates #1682
Updates #1683
Updates #1685
Updates #1699

Change-Id: Iddcfb6c5438e03827049eecbf0a95fae6c078436
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/606784
Reviewed-by: Damien Neil <dneil@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.com>
Auto-Submit: Tatiana Bradley <tatianabradley@google.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module.
Projects
None yet
Development

No branches or pull requests

3 participants