Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2024-21661: Argo CD Denial of Service (DoS) Vulnerability Due to Unsafe Array Modification in Multi-threaded Environment

HighCVSS 7.5 · v3.1—No exploit Fix available

Noroxi assessment

Priority: Monitor (action score 30/100)

  • The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
  • Probability of exploitation in the next 30 days: 1.1% (FIRST EPSS); higher than 67.9% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: github.com/argoproj/argo-cd/v2 (Go) 2.10.4, 2.9.9, 2.8.13; openshift-gitops-argocd-cli (Red Hat:openshift_gitops:1.12::el8) 0:1.12.1-5.el8; openshift-gitops-argocd-cli-redistributable (Red Hat:openshift_gitops:1.12::el8) 0:1.12.1-5.el8.
  • Mentioned 1 time in Turkish national cyber security advisories (siberguvenlik.gov.tr).

Low priority for now. Upgrade to github.com/argoproj/argo-cd/v2 (Go) 2.10.4, 2.9.9, 2.8.13; openshift-gitops-argocd-cli (Red Hat:openshift_gitops:1.12::el8) 0:1.12.1-5.el8; openshift-gitops-argocd-cli-redistributable (Red Hat:openshift_gitops:1.12::el8) 0:1.12.1-5.el8 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. Prior to versions 2.8.13, 2.9.9, and 2.10.4, an attacker can exploit a critical flaw in the application to initiate a Denial of Service (DoS) attack, rendering the application inoperable and affecting all users. The issue arises from unsafe manipulation of an array in a multi-threaded environment. The vulnerability is rooted in the application's code, where an array is being modified while it is being iterated over. This is a classic programming error but becomes critically unsafe when executed in a multi-threaded environment. When two threads interact with the same array simultaneously, the application crashes. This is a Denial of Service (DoS) vulnerability. Any attacker can crash the application continuously, making it impossible for legitimate users to access the service. The issue is exacerbated because it does not require authentication, widening the pool of potential attackers. Versions 2.8.13, 2.9.9, and 2.10.4 contain a patch for this issue.

Published
Mar 18, 2024
Updated
Jun 17, 2026
EPSS
1.1% · 67th percentile

Report tools

JSON

Action score

30

Monitor

Low priority for now.

CVSS
30 / 40 · 7.5 / 10
CISA KEV
0 / 30 · Not listed
EPSS
0 / 30 · 1.1%

CISA SSVC decision

Exploitation
proof of concept
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
7.5
CNA · GitHub_M
7.5
agree

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

  • Not in KEV: no record of exploitation in the wild
  • No public exploit code on record
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2024-21661

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits every 10 minutes on paid plans, on the hour on the free plan.

Your free account also gets you

  • CVE alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools, at most 30 a day (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
argoprojargo cd

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • argoproj argo-cd

    • < 2.8.13, >= 2.9.0, < 2.9.9, >= 2.10.0, < 2.10.4affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • argoproj argo cdbefore 2.8.13
  • argoproj argo cd2.9.0 and later · before 2.9.9
  • argoproj argo cd2.10.0 and later · before 2.10.4

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
Gogithub.com/argoproj/argo-cdup to and including 1.8.7—
Gogithub.com/argoproj/argo-cd/v2from 2.10.0 · before 2.10.42.10.4
Gogithub.com/argoproj/argo-cd/v2from 2.9.0 · before 2.9.92.9.9
Gogithub.com/argoproj/argo-cd/v2before 2.8.132.8.13
Red Hat:openshift_gitops:1.12::el8openshift-gitops-argocd-clibefore 0:1.12.1-5.el80:1.12.1-5.el8
Red Hat:openshift_gitops:1.12::el8openshift-gitops-argocd-cli-redistributablebefore 0:1.12.1-5.el80:1.12.1-5.el8
Red Hat:openshift_gitops:1.12::el9microshift-gitopsbefore 0:1.12.1-4.el90:1.12.1-4.el9
Red Hat:openshift_gitops:1.12::el9microshift-gitops-release-infobefore 0:1.12.1-4.el90:1.12.1-4.el9
Red Hat:openshift_gitops:1.12::el9openshift-gitops-argocd-clibefore 0:1.12.1-4.el90:1.12.1-4.el9
Red Hat:openshift_gitops:1.12::el9openshift-gitops-argocd-cli-redistributablebefore 0:1.12.1-4.el90:1.12.1-4.el9

Other highest-scoring records for the same primary product.

  • CVE-2025-55190Argo CD: Project API Token Exposes Repository Credentials
    41Plan
  • CVE-2022-29165Argo CD will blindly trust JWT claims if anonymous access is enabled
    41Plan
  • CVE-2024-21652Argo CD vulnerable to Bypassing of Brute Force Protection via Application Crash and In-Memory Data Loss
    39Monitor

Published before and after this one in the same product

  • ← EarlierCVE-2023-50726Mar 13, 2024 · Users with `create` but not `override` privileges can perform local sync in argo-cd
    25Monitor
  • ← EarlierCVE-2024-28175Mar 13, 2024 · Cross-site scripting on application summary component in argo-cd
    21Monitor
  • Later →CVE-2024-21662Mar 18, 2024 · Argo CD vulnerable to Bypassing of Rate Limit and Brute Force Protection Using Cache Overflow
    36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
Go:github.com/argoproj/argo-cd/v22.10.4Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.8.13Package registry (OSV)
Go:github.com/argoproj/argo-cd/v22.9.9Package registry (OSV)
red hat:microshift-gitops0:1.12.1-4.el9 · Red Hat:openshift_gitops:1.12::el9Package registry (OSV)
red hat:microshift-gitops-release-info0:1.12.1-4.el9 · Red Hat:openshift_gitops:1.12::el9Package registry (OSV)
red hat:openshift-gitops-argocd-cli0:1.12.1-5.el8 · Red Hat:openshift_gitops:1.12::el8Package registry (OSV)
red hat:openshift-gitops-argocd-cli-redistributable0:1.12.1-5.el8 · Red Hat:openshift_gitops:1.12::el8Package registry (OSV)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

National notice (Türkiye Cybersecurity Directorate / USOM)

Official security notices citing this record; remediation advice is on the agency's page.

All national notices →

Not on record for this CVE: EPSS history · researcher credit · variant or chain candidate · public bounty program.

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
none
Integrity
none
Availability
high · the service can be disrupted
Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Unchanged
Confidentiality impact
None
Integrity impact
None
Availability impact
High

Weakness class (CWE)

CWE-787 · Out-of-bounds Write

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

nvd-primary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

MITRE has no CAPEC/ATT&CK mapping for this CWE.

References

All records