CVE-2020-11576 json
Observable Discrepancy in Argo
published 2020-04-08 6 y ago modified 2026-06-17 4 mo ago also BIT-argo-cd-2020-11576 , EUVD-2021-2593 , GHSA-vj54-cjrx-x696 , GO-2022-0882
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 80%
- public exploits
- 0
- none known
Summary
Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames of valid (non-SSO) accounts because /api/v1/session returned 401 for an existing username and 404 otherwise.
Patch / fix
- go github.com/argoproj/argo-cd 1.5.1
- github.com/argoproj/argo-cd@35a7350 commit
- github.com/argoproj/argo-cd#3215 pull request
Exploit prediction
1.97% chance of exploitation in the next 30 days, higher than 80% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| GitHub | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| OSV | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/argoproj/argo-cd | >=1.5.0, <1.5.1 |
1.5.1 |
| bitnami | argo-cd | >=1.5.0, <=1.5.0 |
no fix listed |
Classification
- Weakness
-
- CWE-203 Observable Discrepancy
References
-
github.com
/argoproj/argo-cd/pull/3215
web, patch, third-party-advisory
-
github.com
/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1
web, patch, third-party-advisory
-
soluble.ai
/blog/argo-cves-2020
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2020-11576
advisory
-
github.com
/advisories/GHSA-vj54-cjrx-x696
advisory
Sources
- CVE List CVE-2020-11576
- GitHub Advisory GHSA-vj54-cjrx-x696
- NVD CVE-2020-11576
- OSV BIT-argo-cd-2020-11576
- OSV GO-2022-0882
Fencer Vulns 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.