Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2022-41354 medium CVSS 4.3

Vulnerability in github.com/argoproj/argo-cd (CVE-2022-41354)

Summary

Vulnerability in github.com/argoproj/argo-cd (CVE-2022-41354). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 2.4.28 or later.

Original description

The description as published by the source.

Impact

All versions of Argo CD starting with v0.5.0 are vulnerable to an information disclosure bug allowing unauthorized users to enumerate application names by inspecting API error messages. An attacker could use the discovered application names as the starting point of another attack. For example, the attacker might use their knowledge of an application name to convince an administrator to grant higher privileges (social engineering).

Many Argo CD API endpoints accept an application name as the only parameter. Since Argo CD RBAC requires both the application name and its configured project name (and, if apps-in-any-namespace is enabled, the application's namespace), Argo CD fetches the requested application before performing the RBAC check. If the application does not exist, the API returns a "not found". If the application does exist, and the user does not have access, the API returns an "unauthorized" error. By trial and error, an attacker can infer which applications exist and which do not.

Note that application resources are not fetched for API calls from unauthenticated users. If your Argo CD instance is accessible from the public internet, unauthenticated users will not be able to cause Argo CD to make Kubernetes API calls.

The patch changes API behavior to return "unauthorized" both when the application is missing and when the user is not authorized to access it. This change in API behavior may impact API clients. Check your code to make sure it will h…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2022-41354 has been found in github.com/argoproj/argo-cd.
Risk of unauthorized operations or information disclosure. CVSS score: 4.3/10.
What to do: upgrade github.com/argoproj/argo-cd to 2.4.28 or later.
If unsure, ask your IT team or search "github.com/argoproj/argo-cd CVE-2022-41354" on the vendor's site.

CVE-2022-41354 (github.com/argoproj/argo-cd) — CWE-203 / CVSS v3 4.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 2.4.28 — apply immediately
Workaround: There are no workarounds besides upgrading.
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-203) exists in github.com/argoproj/argo-cd.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/argoproj/argo-cd.

🔥 Severity

Severity: Medium (CVSS 4.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 2.4.28.

🛡️ Workaround

Workaround: There are no workarounds besides upgrading.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/argoproj/argo-cd' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'github.com/argoproj/argo-cd' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/argoproj/argo-cd を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    There are no workarounds besides upgrading.

    パッチが適用されるまでの応急処置として、There are no workarounds besides upgrading. を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade github.com/argoproj/argo-cd to 2.4.28

    ステージング環境で 2.4.28 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/argoproj/argo-cd
[{"type":"SEMVER","events":[{"introduced":"0.5.0"},{"last_affected":"1.8.7"}]}]
Go github.com/argoproj/argo-cd/v2
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"2.4.28"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details