# CVE-2024-31989: ArgoCD Vulnerable to Use of Risky or Missing Cryptographic Algorithms in Redis Cache > Unauthenticated access to Redis allows privilege escalation and data leakage in ArgoCD deployments lacking strict network policies. - **Severity:** Critical 9.1 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 21 May 2024 - **Updated:** 2 Aug 2024 - **Also known as:** BIT-argo-cd-2024-31989, GHSA-9766-5277-j5hr, GO-2024-2877 ## What is CVE-2024-31989? CVE-2024-31989 is a critical vulnerability in Argoproj Argo Cd, published on 21 May 2024. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. It has been discovered that an unprivileged pod in a different namespace on the same cluster could connect to the Redis server on port 6379. Despite having installed the latest version of the VPC CNI plugin on the EKS cluster, it requires manual enablement through configuration to enforce network policies. This raises concerns that many clients might unknowingly have open access to their Redis servers. This vulnerability could lead to Privilege Escalation to the level of cluster controller, or to information leakage, affecting anyone who does not have strict access controls on their Redis instance. This issue has been patched in version(s) 2.8.19, 2.9.15 and 2.10.10. Weakness: CWE-327 (Use of a Broken or Risky Cryptographic Algorithm) ## Which versions are affected by CVE-2024-31989? 13 open source packages ship an affected version, including github.com/argoproj/argo-cd/v2, argo-cd and github.com/argoproj/argo-cd. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.8.19, 2.9.15, 2.10.10, 2.11.1 | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.8.19 | | `github.com/argoproj/argo-cd/v2` | Go | All versions | 2.8.19 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0-rc1 | 2.10.10 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.10.0-rc1 | 2.10.10 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.11.0-rc1 | 2.11.1 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.11.0-rc1 | 2.11.1 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0-rc1 | 2.9.15 | | `github.com/argoproj/argo-cd/v2` | Go | From 2.9.0-rc1 | 2.9.15 | | `argo-cd` | Bitnami | All versions | 2.11.1 | | `github.com/argoproj/argo-cd` | Go | All versions | None | | `github.com/argoproj/argo-cd` | Go | All versions to 1.8.7 | None | | `github.com/argoproj/argo-cd` | Go | All versions to 1.8.7 | None | Products: Argoproj Argo Cd. ## How do I fix CVE-2024-31989? Upgrade github.com/argoproj/argo-cd/v2 to a fixed version for your release line: 2.8.19, 2.9.15, 2.10.10 or 2.11.1. ## Is CVE-2024-31989 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31989 exists. Public exploit code: - Exploit for CVE-2024-31989. (github_poc): https://github.com/vt0x78/CVE-2024-31989 ## 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-2024-31989 and fix it if it is affected. What it is: CVE-2024-31989 is a critical vulnerability in Argoproj Argo Cd, published on 21 May 2024. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-31989 exists. Affected packages and fixed versions: - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.8.19, 2.9.15, 2.10.10, 2.11.1 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.8.19 - github.com/argoproj/argo-cd/v2 (Go): affected all versions; fixed in 2.8.19 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0-rc1; fixed in 2.10.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.10.0-rc1; fixed in 2.10.10 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.11.0-rc1; fixed in 2.11.1 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.11.0-rc1; fixed in 2.11.1 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0-rc1; fixed in 2.9.15 - github.com/argoproj/argo-cd/v2 (Go): affected from 2.9.0-rc1; fixed in 2.9.15 - argo-cd (Bitnami): affected all versions; fixed in 2.11.1 - github.com/argoproj/argo-cd (Go): affected all versions; no fix listed - github.com/argoproj/argo-cd (Go): affected all versions up to 1.8.7; 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-2024-31989/ (Markdown: https://insights.sbomify.com/CVE-2024-31989/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-31989 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-31989 - OSV: https://osv.dev/vulnerability/CVE-2024-31989 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-31989/ Summaries are generated and may contain mistakes; the official description above is the record.