GHSA-2gvw-w6fj-7m3c BIT-argo-cd-2024-31990 CVE-2024-31990 GO-2024-2728

Argo CD's API server does not enforce project sourceNamespaces

Medium Go

Severity: 4.8 / 10; Medium · CVSS 3.1
Exploit chance (EPSS): 0.45%; Chance of exploitation in the next 30 days. Higher than 38.70% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-863 Incorrect Authorization
Fix: 2.8.16; Upgrade github.com/argoproj/argo-cd/v2 to this version or later

Description

Impact

I can convince the UI to let me do things with an invalid Application.

Admin gives me p, michael, applications, *, demo/*, allow, where demo can just deploy to the demo namespace
Admin gives me AppProject dev which reconciles from ns dev-apps
Admin gives me p, michael, applications, sync, dev/*, allow, i.e. no updating via the UI allowed, gitops-only
I create an Application called pwn in dev-apps with project dev and sync the app with sources from git
I change the Application’s project to demo via kubectl or gitops (whichever mechanism my admins have given me, because it should be safe)
I use the UI to edit the resource which should only be mutable via gitops

Patches

A patch for this vulnerability has been released in the following Argo CD versions:

v2.10.7 v2.9.12 v2.8.16

For more information

If you have any questions or comments about this advisory:

Open an issue in the Argo CD issue tracker or discussions Join us on Slack in channel #argo-cd

Credits

This vulnerability was found & reported by @crenshaw-dev (Michael Crenshaw)

The Argo team would like to thank these contributors for their responsible disclosure and constructive communications during the resolve of this issue

Affected versions

Go

Package	Vulnerable	Fixed in
github.com/argoproj/argo-cd	`all versions`	No fix yet
github.com/argoproj/argo-cd/v2	`>= 2.4.0, < 2.8.16`	`2.8.16`
github.com/argoproj/argo-cd/v2	`>= 2.9.0, < 2.9.12`	`2.9.12`
github.com/argoproj/argo-cd/v2	`>= 2.10.0, < 2.10.7`	`2.10.7`
github.com/argoproj/argo-cd/v2	`>= 2.4.0, < 2.8.16` `>= 2.9.0, < 2.9.12` `>= 2.10.0, < 2.10.7`	`2.8.16` `2.9.12` `2.10.7`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

github.com/argoproj/argo-cd/v2 Go → `2.8.16`

go

go get github.com/argoproj/argo-cd/v2@v2.8.16 && go mod tidy

Severity breakdown

CVSS 3.1 4.8

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

Attack vector: Network
Attack complexity: High
Privileges required: Low
User interaction: Required
Scope: Unchanged
Confidentiality: None
Integrity: None
Availability: High

Weakness

CWE-863: Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

How to prevent it

Architecture and Design: Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) [REF-229] to enforce the roles at the appropriate boundaries. Note that this approach may not protect against horizontal authorization, i.e., it will not protect a user from attacking others with the same role.
Architecture and Design: Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records. For example, a database may restrict access for medical records to a specific database user, but each record might only be intended to be accessible to the patient and the patient's doctor [REF-7].
Architecture and Design: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using authorization frameworks such as the JAAS Authorization Framework [REF-233] and the OWASP ESAPI Access Control feature [REF-45].
Architecture and Design: For web applications, make sure that the access control mechanism is enforced correctly at the server side on every page. Users should not be able to access any unauthorized functionality or information by simply requesting direct access to that page. One way to do this is to ensure that all pages containing sensitive information are not cached, and that all such pages restrict access to requests that are accompanied by an active and authenticated session token associated with a user who has the required permissions to access that page.
System Configuration, Installation: Use the access control capabilities of your operating system and server environment and define your access control lists accordingly. Use a "default deny" policy when defining these ACLs.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2024-31990

Packages

github.com/argoproj/argo-cd

Timeline

Apr 15, 2024 Published
Aug 7, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-fmxq-cgp8-87wp Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks	Critical	Also affects github.com/argoproj/argo-cd
GHSA-j6cw-g6p4-7hch Argo CD repo-server command injection via crafted SSH repository SOCKS5 proxy URL	High	Also affects github.com/argoproj/argo-cd
GHSA-h98r-wv3h-fr38 Argo CD: Stored XSS in application link annotations enables developer-to-admin privilege escalation	High	Also affects github.com/argoproj/argo-cd
GO-2026-5618 Argo CD: Kubernetes Secret Extraction via ArgoCD ServerSideDiff via sensitive annotations	Medium	Also affects github.com/argoproj/argo-cd
GO-2026-5099 ArgoCD ServerSideDiff is vulnerable to Kubernetes Secret Extraction	Critical	Also affects github.com/argoproj/argo-cd
GHSA-gpx4-37g2-c8pv Argo CD Unauthenticated Remote DoS via malformed Azure DevOps git.push webhook	High	Also affects github.com/argoproj/argo-cd
GHSA-wp4p-9pxh-cgx2 argo-cd vulnerable unauthenticated DoS via malformed Gogs webhook payload	High	Also affects github.com/argoproj/argo-cd
GHSA-f9gq-prrc-hrhc Unauthenticated argocd-server panic via a malicious Bitbucket-Server webhook payload	High	Also affects github.com/argoproj/argo-cd

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor