Skip to content
Fencer Intel
medium 6.3

CVE-2023-25163 json

Argo CD leaks repository credentials in user-facing error messages and in logs

published 3y ago modified 2mo ago also BIT-argo-cd-2023-25163 , EUVD-2023-0745 , GHSA-mv6w-j4xc-qpfw , GO-2023-1548

cvss
6.3
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 58%
public exploits
0
none known

Summary

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.

Patch / fix

  • go github.com/argoproj/argo-cd/v2 2.6.1

Is CVE-2023-25163 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
last yr.

Exploit prediction

0.84% chance of exploitation in the next 30 days, higher than 58% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 6.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
GitHub 3.1 6.3 CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N
NVD 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
OSV 3.1 6.5 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
go github.com/argoproj/argo-cd/v2
>=2.6.0-rc1, <2.6.1
2.6.1
bitnami argo-cd
>=2.6.0, <=2.6.0
>=2.6.0-rc1, <=2.6.0-rc1
>=2.6.0-rc2, <=2.6.0-rc2
>=2.6.0-rc3, <=2.6.0-rc3
>=2.6.0-rc4, <=2.6.0-rc4
>=2.6.0-rc5, <=2.6.0-rc5
>=2.6.0-rc6, <=2.6.0-rc6
>=2.6.0-rc7, <=2.6.0-rc7
no fix listed

Affected products

  • argoproj argo-cd

Classification

Weakness
  • CWE-532 Insertion of Sensitive Information into Log File

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.