Description
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.
Metrics
CVSS 3.1 5.3/10
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:NWeakness enumeration
Affected software
| Vendor | Product | Versions |
|---|---|---|
| n/a | n/a | n/a |
References
- https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1Patch, Third Party Advisory
- https://github.com/argoproj/argo-cd/pull/3215Patch, Third Party Advisory
- https://www.soluble.ai/blog/argo-cves-2020Third Party Advisory
- https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1Patch, Third Party Advisory
- https://github.com/argoproj/argo-cd/pull/3215Patch, Third Party Advisory
- https://www.soluble.ai/blog/argo-cves-2020Third Party Advisory
Timeline
- Published
- Apr 8, 2020
- Last modified
- Jun 17, 2026
- NVD status
- Modified