Skip to content
Fencer Vulns
medium 6.5

CVE-2023-40584 json

Denial of Service to Argo CD repo-server

published 2023-09-07 3 y ago modified 2026-06-17 4 mo ago also BIT-argo-cd-2023-40584 , EUVD-2023-2501 , GHSA-g687-f2gx-6wm8 , GO-2023-2050

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

Summary

Argo CD is a declarative continuous deployment for Kubernetes. All versions of ArgoCD starting from v2.4 have a bug where the ArgoCD repo-server component is vulnerable to a Denial-of-Service attack vector. Specifically, the said component extracts a user-controlled tar.gz file without validating the size of its inner files. As a result, a malicious, low-privileged user can send a malicious tar.gz file that exploits this vulnerability to the repo-server, thereby harming the system's functionality and availability. Additionally, the repo-server is susceptible to another vulnerability due to the fact that it does not check the extracted file permissions before attempting to delete them. Consequently, an attacker can craft a malicious tar.gz archive in a way that prevents the deletion of its inner files when the manifest generation process is completed. A patch for this vulnerability has been released in versions 2.6.15, 2.7.14, and 2.8.3. Users are advised to upgrade. The only way to completely resolve the issue is to upgrade, however users unable to upgrade should configure RBAC (Role-Based Access Control) and provide access for configuring applications only to a limited number of administrators. These administrators should utilize trusted and verified Helm charts.

Patch / fix

  • go github.com/argoproj/argo-cd/v2 2.6.15, 2.7.14, 2.8.3
  • bitnami argo-cd 2.6.15, 2.7.14, 2.8.3
  • argoproj argo_cd 2.6.15, 2.7.14, 2.8.3

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-2023-40584 updated cvss 6.5

ArgoCD: Denial of Service to Argo CD repo-server

  • Red Hat OpenShift GitOps 1.8 openshift-gitops-1/argocd-rhel8 v1.8.5-1
    fixed: vendor fix RHSA-2023:5030
  • Red Hat OpenShift GitOps 1.9 openshift-gitops-1/argocd-rhel8 v1.9.2-2
    fixed: vendor fix RHSA-2023:5029
  • Red Hat OpenShift GitOps 1.8 openshift-gitops-1/dex-rhel8 v1.8.5-1, openshift-gitops-1/gitops-rhel8 v1.8.5-1, openshift-gitops-1/kam-delivery-rhel8 v1.8.5-1, openshift-gitops-1/console-plugin-rhel8 v1.8.5-1, openshift-gitops-1/gitops-rhel8-operator v1.8.5-1, openshift-gitops-1/gitops-operator-bundle v1.8.5-1 Red Hat OpenShift GitOps 1.9 openshift-gitops-1/dex-rhel8 v1.9.2-2, openshift-gitops-1/gitops-rhel8 v1.9.2-2, openshift-gitops-1/must-gather-rhel8 v1.9.2-2, openshift-gitops-1/kam-delivery-rhel8 v1.9.2-2, openshift-gitops-1/argo-rollouts-rhel8 v1.9.2-2, openshift-gitops-1/console-plugin-rhel8 v1.9.2-2, +2 more
    not affected: vulnerable code not present

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
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd/v2
>=2.4.0, <2.6.15
>=2.7.0, <2.7.14
>=2.8.0, <2.8.3
2.6.15
2.7.14
2.8.3
bitnami argo-cd
>=2.4.0, <2.6.15
>=2.7.0, <2.7.14
>=2.8.0, <2.8.3
2.6.15
2.7.14
2.8.3
go github.com/argoproj/argo-cd
all versions
 no fix listed

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-400 Uncontrolled Resource Consumption

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.