# CVE-2023-40025: Argo CD web terminal session doesn't expire > Attackers can maintain active web terminal sessions after token expiration, allowing unauthorized access to sensitive information in Argo CD. - **Severity:** Medium 4.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 23 Aug 2023 - **Updated:** 1 Oct 2024 - **Also known as:** GHSA-c8xw-vjgf-94hr, GO-2023-2018 ## What is CVE-2023-40025? CVE-2023-40025 is a medium-severity authentication bypass vulnerability in Argoproj Argo Cd, published on 23 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting from version 2.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. A patch for this vulnerability has been released in the following Argo CD versions: 2.6.14, 2.7.12 and 2.8.1. Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration) ## Which versions are affected by CVE-2023-40025? 10 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2 and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-20230718200744-12a5a7a70d6e | 2.0.0-20230821201509-e047efa8f951 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.0.0-20230718200744-12a5a7a70d6e | 2.0.0-20230821201509-e047efa8f951 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.6.0 | 2.6.14, 2.7.12, 2.8.1 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.6.0 | 2.6.14 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.6.0 | 2.6.14 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.7.0 | 2.7.12 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.7.0 | 2.7.12 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.8.0 | 2.8.1 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.8.0 | 2.8.1 | | `github.com/argoproj/argo-cd` | Go | All versions | None | Products: Argoproj Argo Cd. ## How do I fix CVE-2023-40025? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.0.0-20230821201509-e047efa8f951, 2.6.14, 2.7.12 or 2.8.1. ## Is CVE-2023-40025 being exploited? There is no known exploitation of CVE-2023-40025 in the wild and no public exploit code. ## Other vulnerabilities in Argoproj Argo Cd - [CVE-2025-55190](https://insights.sbomify.com/CVE-2025-55190/): Argo CD: Project API Token Exposes Repository Credentials (critical 10.0) - [CVE-2022-29165](https://insights.sbomify.com/CVE-2022-29165/): Argo CD will blindly trust JWT claims if anonymous access is enabled (critical 10.0) - [CVE-2023-40029](https://insights.sbomify.com/CVE-2023-40029/): Cluster secret might leak in cluster details page in Argo CD (critical 9.9) - [CVE-2022-24768](https://insights.sbomify.com/CVE-2022-24768/): Improper access control allows admin privilege escalation in Argo CD (critical 9.9) - [CVE-2024-21652](https://insights.sbomify.com/CVE-2024-21652/): Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2023-40025 and fix it if it is affected. What it is: CVE-2023-40025 is a medium-severity authentication bypass vulnerability in Argoproj Argo Cd, published on 23 Aug 2023. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2023-40025 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected from 2.0.0-20230718200744-12a5a7a70d6e; fixed in 2.0.0-20230821201509-e047efa8f951 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.0.0-20230718200744-12a5a7a70d6e; fixed in 2.0.0-20230821201509-e047efa8f951 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.6.0; fixed in 2.6.14, 2.7.12, 2.8.1 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.6.0; fixed in 2.6.14 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.6.0; fixed in 2.6.14 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.7.0; fixed in 2.7.12 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.7.0; fixed in 2.7.12 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.8.0; fixed in 2.8.1 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.8.0; fixed in 2.8.1 - github.com/argoproj/argo-cd (Go): affected all versions; no fix listed Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2023-40025/ (Markdown: https://insights.sbomify.com/CVE-2023-40025/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2023-40025 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-40025 - OSV: https://osv.dev/vulnerability/CVE-2023-40025 --- From sbomify Insights: https://insights.sbomify.com/CVE-2023-40025/ Summaries are generated and may contain mistakes; the official description above is the record.