Username Enumeration in Multiple WSO2 Products with Multi-Attribute Login Enabled
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 5.10.0.346, 5.11.0.395, 6.0.0.231, 6.1.0.223, 2.0.0.390, and 1 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
A username enumeration vulnerability exists in multiple WSO2 products when Multi-Attribute Login is enabled. In this configuration, the system returns a distinct "User does not exist" error message to the login form, regardless of the validate_username setting. This behavior allows malicious actors to determine which usernames exist in the system based on observable discrepancies in the application's responses. Exploitation of this vulnerability could aid in brute-force attacks, targeted phishing campaigns, or other social engineering techniques by confirming the validity of user identifiers within the system.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 Identity Server
From 5.10.0 · fixed in 5.10.0.346; From 5.11.0 · fixed in 5.11.0.395; From 6.0.0 · fixed in 6.0.0.231; From 6.1.0 · fixed in 6.1.0.223
- WSO2 WSO2 Open Banking IAM
From 2.0.0 · fixed in 2.0.0.390
- WSO2 WSO2 Identity Server as Key Manager
From 5.10.0 · fixed in 5.10.0.339
- org.wso2.carbon.identity.framework:org.wso2.carbon.identity.input.validation.mgtMaven
through 7.8.103