When Multi-Attribute Login is enabled, the login interface fails to consistently mask the existence of user accounts

Overview

When Multi-Attribute Login is enabled, the login interface fails to consistently mask the existence of user accounts. For valid users, the server resolves and displays their canonical username, while for non-existent users, it echoes the original input. This occurs regardless of the validate_username configuration.

The discovery of valid usernames can increase the risk of brute force attacks, social engineering attacks, and targeted information leakage. Attackers can leverage this information to craft more effective phishing campaigns or social engineering tactics to compromise user accounts or extract sensitive data.

Affected

• api_manager >= 3.1.0, < 3.1.0.351
• api_manager >= 3.2.0, < 3.2.0.455
• api_manager >= 4.0.0, < 4.0.0.375
• identity_server >= 5.10.0, < 5.10.0.380
• identity_server >= 5.11.0, < 5.11.0.427
• identity_server >= 6.0.0, < 6.0.0.254
• identity_server >= 6.1.0, < 6.1.0.255
• identity_server >= 7.0.0, < 7.0.0.132
• identity_server >= 7.1.0, < 7.1.0.40
• identity_server >= 7.2.0, < 7.2.0.2
• identity_server_as_key_manager >= 5.10.0, < 5.10.0.371
• open_banking_am >= 2.0.0, < 2.0.0.400
• open_banking_iam >= 2.0.0, < 2.0.0.420

Remediation

Upgrade past the affected range:

• api_manager 4.0.0.375
• identity_server 7.2.0.2
• identity_server_as_key_manager 5.10.0.371
• open_banking_am 2.0.0.400
• open_banking_iam 2.0.0.420