CVE-2020-11576: User-enumeration vulnerability in Argo CD

argo-cd Updated 02 Oct 2025

Summary

06/03/2024
No i
Medium
Not published

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 of valid (non-SSO) accounts because /api/v1/session returned 401 for an existing... Affects argo-cd versions >= 1.5.0, <= 1.5.0. No fix is published. How to fix ↓

Also tracked for

The same CVE-2020-11576 is tracked separately for each ecosystem and vendor. Its fix information is the same; the package and affected versions differ.

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Argo CD is a continuous delivery tool that provides a declarative approach for deploying and managing applications in Kubernetes clusters. It allows users to define and automate the deployment process, ensuring consistency and reliability. However, Argo CD version 1.5.0 is vulnerable to a user-enumeration issue, which can expose the usernames of valid (non-SSO) accounts.

Vulnerability Detail

The vulnerability in Argo CD version 1.5.0 arises from the behavior of the /api/v1/session endpoint. When a valid username is provided, the endpoint returns a 401 status code, indicating an authentication failure. On the other hand, if an invalid username is provided, a 404 status code is returned. This discrepancy allows an attacker to enumerate valid usernames by sending requests to the endpoint and observing the response codes. By exploiting this vulnerability, an attacker can gather a list of valid usernames, potentially aiding in further attacks or unauthorized access attempts.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Workaround

There is no specific workaround available for this vulnerability. Upgrading to the fixed version is the recommended solution.

Conclusion

Argo CD version 1.5.0 is vulnerable to a user-enumeration issue, allowing attackers to determine valid usernames of non-SSO accounts. To mitigate this vulnerability, it is crucial to upgrade to Argo CD version 1.5.1 or later. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for argo-cd →

Share this vulnerability

FAQ

Argo CD is a continuous delivery tool for Kubernetes that automates the deployment process and ensures application consistency.

The vulnerability allows attackers to determine valid usernames of non-SSO accounts, potentially aiding in unauthorized access attempts.

Argo CD version 1.5.0 is affected by this vulnerability.

To fix this vulnerability, upgrade to Argo CD version 1.5.1 or later.

No, upgrading to the fixed version is the recommended solution.

Related vulnerabilities

Recent vulnerabilities recorded for argo-cd.

How To Fix

No fixed version is published for this vulnerability.

Tip — Not sure whether your app is affected? Vulert can check the versions your app actually runs. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback