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/argoproj/argo-cd: CVE-2022-31036 #499

Closed
GoVulnBot opened this issue Jun 27, 2022 · 2 comments
Closed
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

CVE-2022-31036 references github.com/argoproj/argo-cd, which may be a Go module.

Description:
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v1.3.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive YAML files from Argo CD's repo-server. A malicious Argo CD user with write access for a repository which is (or may be) used in a Helm-type Application may commit a symlink which points to an out-of-bounds file. If the target file is a valid YAML file, the attacker can read the contents of that file. Sensitive files which could be leaked include manifest files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any YAML-formatted secrets which have been mounted as files on the repo-server. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. If you are using a version >=v2.3.0 and do not have any Helm-type Applications you may disable the Helm config management tool as a workaround.

Links:

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

packages:
  - module: github.com/argoproj/argo-cd
    package: argo-cd
description: |+
    Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v1.3.0 are vulnerable to a symlink following bug allowing a malicious user with repository write access to leak sensitive YAML files from Argo CD's repo-server. A malicious Argo CD user with write access for a repository which is (or may be) used in a Helm-type Application may commit a symlink which points to an out-of-bounds file. If the target file is a valid YAML file, the attacker can read the contents of that file. Sensitive files which could be leaked include manifest files from other Applications' source repositories (potentially decrypted files, if you are using a decryption plugin) or any YAML-formatted secrets which have been mounted as files on the repo-server. Patches for this vulnerability has been released in the following Argo CD versions: v2.4.1, v2.3.5, v2.2.10 and v2.1.16. If you are using a version >=v2.3.0 and do not have any Helm-type Applications you may disable the Helm config management tool as a workaround.

cves:
  - CVE-2022-31036
links:
    commit: https://github.com/argoproj/argo-cd/commit/04c305396458508a31d03d44afea07b1c620d7cd
    context:
      - https://github.com/argoproj/argo-cd/security/advisories/GHSA-q4w5-4gq2-98vm

@neild neild self-assigned this Jul 11, 2022
@neild
Copy link
Contributor

neild commented Jul 11, 2022

Vulnerability in tool.

@neild neild closed this as completed Jul 11, 2022
@neild neild added excluded: EFFECTIVELY_PRIVATE This vulnerability exists in a package can be imported, but isn't meant to be outside that module. and removed NotGoVuln labels Aug 10, 2022
@gopherbot
Copy link
Contributor

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

gopherbot pushed a commit that referenced this issue Aug 21, 2024
  - data/reports/GO-2022-0457.yaml
  - data/reports/GO-2022-0458.yaml
  - data/reports/GO-2022-0459.yaml
  - data/reports/GO-2022-0471.yaml
  - data/reports/GO-2022-0473.yaml
  - data/reports/GO-2022-0480.yaml
  - data/reports/GO-2022-0482.yaml
  - data/reports/GO-2022-0483.yaml
  - data/reports/GO-2022-0490.yaml
  - data/reports/GO-2022-0491.yaml
  - data/reports/GO-2022-0494.yaml
  - data/reports/GO-2022-0495.yaml
  - data/reports/GO-2022-0496.yaml
  - data/reports/GO-2022-0497.yaml
  - data/reports/GO-2022-0498.yaml
  - data/reports/GO-2022-0499.yaml
  - data/reports/GO-2022-0500.yaml
  - data/reports/GO-2022-0501.yaml
  - data/reports/GO-2022-0502.yaml
  - data/reports/GO-2022-0505.yaml

Updates #457
Updates #458
Updates #459
Updates #471
Updates #473
Updates #480
Updates #482
Updates #483
Updates #490
Updates #491
Updates #494
Updates #495
Updates #496
Updates #497
Updates #498
Updates #499
Updates #500
Updates #501
Updates #502
Updates #505

Change-Id: I92c5f4afd83bb1c6bd9f448bc65ca730c64ce770
Reviewed-on: https://go-review.googlesource.com/c/vulndb/+/607219
Auto-Submit: Tatiana Bradley <tatianabradley@google.com>
Reviewed-by: Damien Neil <dneil@google.com>
LUCI-TryBot-Result: Go LUCI <golang-scoped@luci-project-accounts.iam.gserviceaccount.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