As of v1.5.0, the default admin password is set to the argocd-server pod name. For insiders with access to the cluster or logs, this issue could be abused for privilege escalation, as Argo has privileged roles. A malicious insider is the most realistic threat, but pod names are not meant to be kept secret and could wind up just about anywhere.
The product initializes or sets a resource with a default that is intended to be changed by the administrator, but the default is not secure.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Argo_cd | Argoproj | * | 1.5.0 (excluding) |
Developers often choose default values that leave the product as open and easy to use as possible out-of-the-box, under the assumption that the administrator can (or should) change the default value. However, this ease-of-use comes at a cost when the default is insecure and the administrator does not change it.