Denial of Service (DoS) Vulnerability Due to Unsafe Array Modification in Multi-threaded Environment

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2024-21661: 1.18% estimated exploitation activity in the next 30 days; percentile 67.62 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary 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. Details 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. The core issue is located in expireOldFailedAttempts function: The function modifies the array while iterating it which means the code will cause an error and crash the application pod, inspecting the logs just before the crash we can confirm: PoC To reproduce the vulnerability, you can use the following steps: 1. Launch the application. 2. Trigger the code path that results in the…

Published by the source

18 Mar 2024, 20:28 UTC

Last modified by the source

28 May 2024, 17:58 UTC

Source last checked

26 Oct 2026, 15:04 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6v85-wr92-q4p7

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2024-21661

Advisory: Denial of Service (DoS) Vulnerability Due to Unsafe Array Modification in Multi-threaded Environment
IDs: CVE-2024-21661, GHSA-6v85-wr92-q4p7
Record: https://patchnext.com/advisories/cve-2024-21661 (revision 1, source checked 26 Oct 2026, 15:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/argoproj/argo-cd/v2 2.10.4, 2.9.9, 2.8.13. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/argoproj/argo-cd/v2: affected < 2.8.13; >= 2.9.0, < 2.9.9; >= 2.10.0, < 2.10.4; fixed in 2.9.9, 2.8.13, 2.10.4
- Go github.com/argoproj/argo-cd: affected <= 1.8.7

## Suggested inspection (read-only)
- Go github.com/argoproj/argo-cd/v2: check the installed version with your package manager.
- Go github.com/argoproj/argo-cd: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/argoproj/argo-cd/v2, github.com/argoproj/argo-cd.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6v85-wr92-q4p7 (GitHub-reviewed advisory GHSA-6v85-wr92-q4p7 lists affected ranges: Go github.com/argoproj/argo-cd >=0 =0 =2.9.0 =2.10.0 <2.10.4)

Commands are suggestions: review each one before running it.