| Package | Affected versions | Patched versions |
|---|---|---|
| github.com/argoproj/argo-cd | ≥ 0.7.0, < 2.1.16≥ 0.7.0 | 2.1.16 |
| github.com/argoproj/argo-cd/v2 | ≥ 2.2.0, < 2.2.10≥ 2.3.0, < 2.3.5≥ 2.4.0, < 2.4.1< 2.1.16 | 2.2.102.3.52.4.12.1.16 |
| argo cd | ≥ 0.7.0, < 2.1.16≥ 2.2.0, < 2.2.10≥ 2.3.0, < 2.3.5≥ 2.4.0, < 2.4.1 | 2.1.162.2.102.3.52.4.1 |
All versions of Argo CD starting with v0.7.0 are vulnerable to an uncontrolled memory consumption bug, allowing an authorized malicious user to crash the repo-server service. The repo-server is a critical component of Argo CD, so crashing the repo-server effectively denies core Argo CD services (such as syncing Application updates).
To achieve denial of service, the attacker must be an authenticated Argo CD user authorized to deploy Applications from a repository which contains (or can be made to contain) a large file.
A patch for this vulnerability has been released in the following Argo CD versions:
The patch introduces a new reposerver.max.combined.directory.manifests.size config parameter, which you should tune before upgrading in production. It caps the maximum total file size of .yaml/.yml/.json files in directory-type (raw manifest) Applications. The default max is 10M per Application. This max is designed to keep any single app from consuming more than 3G of memory in the repo-server (manifests consume more space in memory than on disk). The 300x ratio assumes a maliciously-crafted manifest file. If you only want to protect against accidental excessive memory use, it is probably safe to use a smaller ratio.
If your organization uses directory-type Applications with very many manifests or very large manifests then check the size of those manifests and tune the config parameter before deploying this change to production. When testing, make sure to do a "hard refresh" in either the CLI or UI to test your directory-type App. That will make sure you're using the new max logic instead of relying on cached manifest responses from Redis.
There is no workaround besides upgrading.
To mitigate the issue, carefully limit 1) who can configure repos (determined by RBAC), 2) which repos are allowed (determined by Project limitations), and 3) who has push access to those repos (determined by your SCM provider configuration).
Disclosed by ADA Logics in a security audit of the Argo project sponsored by CNCF and facilitated by OSTIF. Thanks to Adam Korczynski and David Korczynski for their work on the audit.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free