Description

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.

Quick Facts

References

• https://github.com/argoproj/argo-cd/commit/1149cdc6e932208c4…
• https://github.com/argoproj/argo-cd/commit/4bc8085b0a6d2296b…
• https://github.com/argoproj/argo-cd/commit/7f0a05834b05103d6…
• https://github.com/argoproj/argo-cd/commit/d5dd7019ee65be889…
• https://github.com/argoproj/argo-cd/releases/tag/v3.3.15
• https://github.com/argoproj/argo-cd/releases/tag/v3.4.10
• https://github.com/argoproj/argo-cd/releases/tag/v3.5.4
• https://github.com/argoproj/argo-cd/releases/tag/v3.6.0-rc2
• https://github.com/argoproj/argo-cd/security/advisories/GHSA…

External Resources