Insertion of Sensitive Information into Log File Affecting github.com/argoproj/argo-cd/util/argo package, versions >=2.6.0-rc1 <2.6.1

Affected versions of this package are vulnerable to Insertion of Sensitive Information into Log File due to having 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.

To mitigate the issue, make sure that the repo credentials have only the least necessary privileges. For example, the credentials should not have push access, and they should not have access to more resources than what Argo CD actually needs (for example, a whole GitHub org when only one repo is needed).

To further mitigate the impact of a leaked write-capable repo credential, users could enable commit signature verification. Even if someone could push a malicious commit, the commit would not by synced.

Users should also enforce least privileges in Argo CD RBAC. Make sure users only have repositories, update, applications, update, or applications, create access if they absolutely need it.

• GitHub Commit
• GitHub Issue
• GitHub PR
• GitHub Release