GitHub Advisoryadvisory · Go

GHSA-c8xw-vjgf-94hr Argo CD web terminal session doesn't expire

HIGH Published 2023-08-23 Modified 2025-06-24 Official page ↗
Aliases
CVE-2023-40025
Ecosystem
Go
Packages
github.com/argoproj/argo-cd/v2
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N
Weaknesses
CWE-613
Reviewed
2023-08-23

Affected packages

• Go github.com/argoproj/argo-cd/v2: >= 2.6.0, < 2.6.14 → fixed in 2.6.14 • Go github.com/argoproj/argo-cd/v2: >= 2.7.0, < 2.7.12 → fixed in 2.7.12 • Go github.com/argoproj/argo-cd/v2: >= 2.8.0, < 2.8.1 → fixed in 2.8.1 • Go github.com/argoproj/argo-cd/v2: >= 2.0.0-20230718200744-12a5a7a70d6e, < 2.0.0-20230821201509-e047efa8f951 → fixed in 2.0.0-20230821201509-e047efa8f951

Description

Impact All versions of Argo CD starting from v2.6.0 have a bug where open web terminal sessions do not expire. This bug allows users to send any websocket messages even if the token has already expired. The most straightforward scenario is when a user opens the terminal view and leaves it open for an extended period. This allows the user to view sensitive information even when they should have been logged out already. Patches A patch for this vulnerability has been released in the following Argo CD version: • v2.6.14 • v2.7.12 • v2.8.1 Workarounds The only way to completely resolve the issue is to upgrade. Mitigations Disable web-based terminal or define RBAC rules to it https://argo-cd.readthedocs.io/en/latest/operator-manual/web_based_terminal/ For more information If you have any questions or comments about this advisory: • Open an issue in the Argo CD issue tracker or discussions • Join us on Slack in channel #argo-cd Credits Thank you to bean.zhang (@zhlu32 ) of HIT-IDS ChunkL Team who discovered the issue and reported it confidentially according to our guidelines.

Related

Weakness · not in database (1)

Alias · CVE (1)

  • CVE-2023-40025 Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. vulnerability

References