Skip to content
Fencer Vulns
critical 9.1

CVE-2024-31989 json

ArgoCD Vulnerable to Use of Risky or Missing Cryptographic Algorithms in Redis Cache

published 2024-05-21 2 y ago modified 2026-09-10 1 mo ago also BIT-argo-cd-2024-31989 , EUVD-2024-1545 , GHSA-9766-5277-j5hr , GO-2024-2877

cvss
9.1
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.5%
EPSS 1.5% chance of exploitation in 30 days, percentile 74%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/argoproj/argo-cd/v2 2.8.19, 2.9.15, 2.10.10, 2.11.1
  • bitnami argo-cd 2.11.1
  • argoproj argo_cd 2.8.19, 2.9.15, 2.10.10, 2.11.1
  • linuxfoundation argo-cd 2.8.19, 2.9.15, 2.10.10, 2.11.1
  • linuxfoundation argo_continuous_delivery 2.8.19, 2.9.15, 2.10.10, 2.11.1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2024-31989 updated cvss 9.6

argocd: Use of Risky or Missing Cryptographic Algorithms in Redis Cache

  • Red Hat OpenShift GitOps 1.10 openshift-gitops-1/dex-rhel8 v1.10.6-4, openshift-gitops-1/argocd-rhel8 v1.10.6-4, openshift-gitops-1/gitops-rhel8 v1.10.6-4, openshift-gitops-1/must-gather-rhel8 v1.10.6-4, openshift-gitops-1/kam-delivery-rhel8 v1.10.6-4, openshift-gitops-1/argo-rollouts-rhel8 v1.10.6-4, +3 more
    fixed: vendor fix RHSA-2024:3369
  • Red Hat OpenShift GitOps 1.11 openshift-gitops-1/dex-rhel8 v1.11.5-3, openshift-gitops-1/argocd-rhel8 v1.11.5-3, openshift-gitops-1/gitops-rhel8 v1.11.5-3, openshift-gitops-1/must-gather-rhel8 v1.11.5-3, openshift-gitops-1/kam-delivery-rhel8 v1.11.5-3, openshift-gitops-1/argo-rollouts-rhel8 v1.11.5-3, +3 more
    fixed: vendor fix RHSA-2024:3475
  • Red Hat OpenShift GitOps 1.12 openshift-gitops-1/dex-rhel8 v1.12.3-4, openshift-gitops-1/argocd-rhel8 v1.12.3-4, openshift-gitops-1/gitops-rhel8 v1.12.3-4, openshift-gitops-1/must-gather-rhel8 v1.12.3-4, openshift-gitops-1/kam-delivery-rhel8 v1.12.3-4, openshift-gitops-1/argo-rollouts-rhel8 v1.12.3-4, +3 more
    fixed: vendor fix RHSA-2024:3368

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
total
Assessed
2 y ago

Exploit prediction

1.48% chance of exploitation in the next 30 days, higher than 74% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/argoproj/argo-cd/security/advisories/GHSA-9766-5277-j5hr referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.1 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
GitHub 3.1 9.0 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
NVD 3.1 9.0 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
OSV 3.1 9.0 CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd/v2
<2.8.19
>=2.9.0-rc1, <2.9.15
>=2.10.0-rc1, <2.10.10
>=2.11.0-rc1, <2.11.1
2.8.19
2.9.15
2.10.10
2.11.1
go github.com/argoproj/argo-cd
<=1.8.7
all versions
 no fix listed
bitnami argo-cd
<2.11.1
2.11.1

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-327 Use of a Broken or Risky Cryptographic Algorithm

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.