CVE-2023-25163: Argo CD leaks repository credentials in user-facing error messages and in logs
(updated )
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.
References
- argo-cd.readthedocs.io/en/stable/operator-manual/rbac
- github.com/advisories/GHSA-mv6w-j4xc-qpfw
- github.com/argoproj/argo-cd
- github.com/argoproj/argo-cd/issues/12309
- github.com/argoproj/argo-cd/pull/12320
- github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw
- nvd.nist.gov/vuln/detail/CVE-2023-25163
- pkg.go.dev/vuln/GO-2023-1548
Detect and mitigate CVE-2023-25163 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →