Critical Argo CD API Vulnerability Exposes Repository Credentials
A critical vulnerability has been identified in Argo CD, which allows API tokens with limited permissions to access sensitive repository credentials. This vulnerability is located in the project details API endpoint and exposes usernames and passwords,…
A critical vulnerability has been identified in Argo CD, which allows API tokens with limited permissions to access sensitive repository credentials. This vulnerability is located in the project details API endpoint and exposes usernames and passwords, compromising the platform's security model by permitting access to secrets without explicit permissions.
The issue originates from an improper authorization check in the Project API, specifically at the /api/v1/projects/{project}/detailed endpoint. API tokens with standard project-level permissions, such as those used for application management, can retrieve all repository credentials linked to that project.
Normally, requests for sensitive information, such as secrets, should require elevated permissions. However, current behavior allows tokens with basic access to retrieve this data.
The vulnerability affects any token with project get permissions, including those with broader global permissions such as p, role/user, projects, get, *, allow . This expands the potential attack surface significantly, as more general-purpose tokens can be exploited.
A critical vulnerability has been identified in Argo CD, which allows API tokens with limited permissions to access sensitive repository credentials.
An attacker with a valid API token with the necessary permissions can make an authenticated call to the detailed project API endpoint. The resulting JSON response will incorrectly include a repositories object containing plaintext username and password credentials for the repositories linked to the project. This enables attackers to easily harvest credentials for accessing private source code repositories.
Consequences of this vulnerability include potential source code theft, malicious code injection into the CI/CD pipeline, and further compromise of development infrastructure.
The Argo CD development team has addressed the issue and released patches. Administrators are advised to upgrade to one of the following secure versions immediately to mitigate the risk:
Upgrading to a patched version will ensure that the API endpoint properly enforces permission checks and prevents unauthorized disclosure of repository credentials.
Based on reporting by Cyber Security News.
