Description
The check user account lock states feature within the email OTP flow fails to validate user input, allowing an attacker to infer the existence of registered user accounts. The discovery of valid usernames can increase the risk of brute-force and social engineering attacks. Attackers can leverage this information to craft targeted phishing campaigns or other malicious activities aimed at tricking users into divulging sensitive data, potentially damaging the organization's reputation and leading to regulatory non-compliance and financial consequences.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
WSO2 WSO2 Identity Server
Default version status: unaffected
0 to < 5.10.0unknown5.10.0 to < 5.10.0.379affected5.11.0 to < 5.11.0.426affected5.11.0 to < 5.11.0.431affected6.0.0 to < 6.0.0.253affected6.1.0 to < 6.1.0.254affected7.0.0 to < 7.0.0.131affected
WSO2 WSO2 Open Banking IAM
Default version status: unaffected
0 to < 2.0.0unknown2.0.0 to < 2.0.0.318affected
WSO2 WSO2 Identity Server as Key Manager
Default version status: unaffected
0 to < 5.10.0unknown5.10.0 to < 5.10.0.267affected
WSO2 Email OTP Authenticator
Default version status: unknown
1.0.18 to < 1.0.18.7affected1.0.24 to ≤ *unaffected
WSO2 WSO2 Carbon Authenticator Library For EmailOTP
Default version status: unknown
4.1.0 to < 4.1.0.8affected4.1.4 to < 4.1.4.9affected4.1.22 to ≤ *unaffected
WSO2 WSO2 Carbon Authenticator Library For EmailOTP
Default version status: unknown
3.0.5 to < 3.0.5.8affected3.0.24 to < 3.0.24.6affected3.0.26 to < 3.0.26.16affected