github.com/argoproj/argo-cd/v2
Affected
- introduced
2.4.0, fixed2.8.16(semver)
Fixed versions
2.8.16
Fix
- Fixed version
2.8.16go get github.com/argoproj/argo-cd/[email protected]
Advisory
Also known as: BIT-argo-cd-2024-31990, CVE-2024-31990, GO-2024-2728
Argo CD's API server does not enforce project sourceNamespaces
Impact
I can convince the UI to let me do things with an invalid Application.
p, michael, applications, *, demo/*, allow, where demo can just deploy to the demo namespacedev which reconciles from ns dev-appsp, michael, applications, sync, dev/*, allow, i.e. no updating via the UI allowed, gitops-onlypwn in dev-apps with project dev and sync the app with sources from gitPatches
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
Medium Basis: The source's own band: MODERATE
2.4.0, fixed 2.8.16 (semver)2.8.16
2.8.16go get github.com/argoproj/argo-cd/[email protected]2.9.0, fixed 2.9.12 (semver)2.9.12
2.9.12go get github.com/argoproj/argo-cd/[email protected]2.10.0, fixed 2.10.7 (semver)2.10.7
2.10.7go get github.com/argoproj/argo-cd/[email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0