Username Enumeration via Authentication Endpoint in WSO2 Identity Server Allows User Account Discovery
- 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 7.0.0.134, 7.1.0.42, 1.0.5.3, 1.0.10.2, 1.0.18.8, 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
The authentication endpoint of WSO2 Identity Server fails to provide a consistent system response when a username does not exist in the system, allowing attackers to differentiate between valid and invalid usernames. This difference in responses can be leveraged to enumerate existing user accounts. Successful exploitation enables an attacker to discover valid usernames within the system, significantly increasing the risk of subsequent attacks such as brute force attacks on user credentials, social engineering attacks, and information leakage. The discovered usernames can be used to craft targeted phishing emails or other social engineering campaigns.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 Identity Server
From 7.0.0 · fixed in 7.0.0.134; From 7.1.0 · fixed in 7.1.0.42
- org.wso2.carbon.identity.auth.otp.commons:org.wso2.carbon.identity.auth.otp.core
From 1.0.5 · fixed in 1.0.5.3; From 1.0.10 · fixed in 1.0.10.2
- org.wso2.carbon.identity.local.auth.emailotp:org.wso2.carbon.identity.local.auth.emailotp
From 1.0.18 · fixed in 1.0.18.8; From 1.0.30 · fixed in 1.0.30.5