CVE-2023-25163
published 2023-02-08CVE-2023-25163: 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…
PriorityP336medium6.5CVSS 3.1
AVNACLPRLUINSUCHINAN
EPSS
0.84%
53.3th percentile
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.
Affected
3 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| argoproj | argo-cd | — | — |
| argoproj | argo_cd | — | — |
| github.com | argoproj_argo-cd_v2 | >= 2.6.0-rc1 < 2.6.1 | 2.6.1 |
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
OSV
Repository access credential leak in github.com/argoproj/argo-cd/v2
osv·2023-02-15
CVE-2023-25163 Repository access credential leak in github.com/argoproj/argo-cd/v2
Repository access credential leak in github.com/argoproj/argo-cd/v2
Argo CD has 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 for
GHSA
Argo CD leaks repository credentials in user-facing error messages and in logs
ghsa·2023-02-08
CVE-2023-25163 [MEDIUM] CWE-532 Argo CD leaks repository credentials in user-facing error messages and in logs
Argo CD leaks repository credentials in user-facing error messages and in logs
### Impact
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
OSV
Argo CD leaks repository credentials in user-facing error messages and in logs
osv·2023-02-08
CVE-2023-25163 [MEDIUM] Argo CD leaks repository credentials in user-facing error messages and in logs
Argo CD leaks repository credentials in user-facing error messages and in logs
### Impact
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
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/https://github.com/argoproj/argo-cd/issues/12309https://github.com/argoproj/argo-cd/pull/12320https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfwhttps://argo-cd.readthedocs.io/en/stable/operator-manual/rbac/https://github.com/argoproj/argo-cd/issues/12309https://github.com/argoproj/argo-cd/pull/12320https://github.com/argoproj/argo-cd/security/advisories/GHSA-mv6w-j4xc-qpfw
2023-02-08
Published