Skip to content

Argo CD web terminal session doesn't expire

High severity GitHub Reviewed Published Aug 23, 2023 in argoproj/argo-cd • Updated Nov 7, 2023

Package

gomod github.com/argoproj/argo-cd (Go)

Affected versions

>= 2.6.0, < 2.6.14
>= 2.7.0, < 2.7.12
= 2.8.0

Patched versions

2.6.14
2.7.12
2.8.1

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:

Credits

Thank you to bean.zhang (@zhlu32 ) of HIT-IDS ChunkL Team who discovered the issue and reported it confidentially according to our guidelines.

References

@crenshaw-dev crenshaw-dev published to argoproj/argo-cd Aug 23, 2023
Published to the GitHub Advisory Database Aug 23, 2023
Reviewed Aug 23, 2023
Published by the National Vulnerability Database Aug 23, 2023
Last updated Nov 7, 2023

Severity

High

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N

EPSS score

0.067%
(32nd percentile)

Weaknesses

CVE ID

CVE-2023-40025

GHSA ID

GHSA-c8xw-vjgf-94hr

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.