Argo CD is a declarative, GitOps continuous delivery tool for Kubernetes. All versions of Argo CD starting with v2.6.0-rc1 have an output sanitization bug which leaks repository access credentials in error messages. These error messages are visible to the user, and they are logged. The error message is visible when a user attempts to create or update an Application via the Argo CD API (and therefor the UI or CLI). The user must have applications, create or applications, update RBAC access to reach the code which may produce the error. The user is not guaranteed to be able to trigger the error message. They may attempt to spam the API with requests to trigger a rate limit error from the upstream repository. If the user has repositories, update access, they may edit an existing repository to introduce a URL typo or otherwise force an error message. But if they have that level of access, they are probably intended to have access to the credentials anyway. A patch for this vulnerability has been released in version 2.6.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
| Name | Vendor | Start Version | End Version |
|---|---|---|---|
| Argo_cd | Argoproj | 2.6.0 (including) | 2.6.0 (including) |
| Argo_cd | Argoproj | 2.6.0-rc1 (including) | 2.6.0-rc1 (including) |
| Argo_cd | Argoproj | 2.6.0-rc2 (including) | 2.6.0-rc2 (including) |
| Argo_cd | Argoproj | 2.6.0-rc3 (including) | 2.6.0-rc3 (including) |
| Argo_cd | Argoproj | 2.6.0-rc4 (including) | 2.6.0-rc4 (including) |
| Argo_cd | Argoproj | 2.6.0-rc5 (including) | 2.6.0-rc5 (including) |
| Argo_cd | Argoproj | 2.6.0-rc6 (including) | 2.6.0-rc6 (including) |
| Argo_cd | Argoproj | 2.6.0-rc7 (including) | 2.6.0-rc7 (including) |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: