Argoproj argo-cd
Argo CD: AppProject destination-namespace and resource restrictions bypassed by PreDelete/PostDelete resource hooks
Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. From 2.10.0 until 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2, Argo CD creates PostDelete resource hooks without applying the AppProject destination and resource authorization checks used during ordinary synchronization. The omitted checks include cluster-scoped and namespaced resource allow/deny lists. A user who can write to an Application's Git repository can commit a delete hook targeting a forbidden namespace, server, group, kind, or resource name, and deletion of the Application causes the application-controller to create that resource with its destination-cluster credentials. The reachable impact is bounded by the controller's cluster access but can include cluster-scoped resources, disallowed namespaces, persistent hook objects, and secondary objects created by a hook Job. PreSync, Sync, PostSync, and SyncFail hooks continue to use the normal project checks. This issue is fixed in versions 3.3.15, 3.4.10, 3.5.4, and 3.6.0-rc2.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 2.10.0, <= 2.14.21
- >= 3.0.0, < 3.3.15
- >= 3.4.0, < 3.4.10
- >= 3.5.0, < 3.5.4
- >= 3.6.0-rc1, < 3.6.0-rc2
Fixed in 3.3.15, 3.4.10, 3.5.4, 3.6.0-rc2
Mitigation
Upgrade argo-cd to 3.3.15 or 3.4.10 or 3.5.4 or 3.6.0-rc2 or later.
References
- Vendor advisory github.com/argoproj/argo-cd/security/advisorie…
- Patch github.com/argoproj/argo-cd/commit/1149cdc6e93…
- Patch github.com/argoproj/argo-cd/commit/4bc8085b0a6…
5 more
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.