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.
CVSS breakdown
CVSS 3.1
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
Affected products
- WSO2 / Email OTP Authenticator1.0.24 – *
- WSO2 / Email OTP Authenticator1.0.18 – 1.0.18.7
- WSO2 / WSO2 Carbon Authenticator Library For EmailOTP4.1.22 – *
- WSO2 / WSO2 Carbon Authenticator Library For EmailOTP4.1.0 – 4.1.0.8
- WSO2 / WSO2 Carbon Authenticator Library For EmailOTP4.1.4 – 4.1.4.9
- WSO2 / WSO2 Carbon Authenticator Library For EmailOTP3.0.24 – 3.0.24.6
- WSO2 / WSO2 Carbon Authenticator Library For EmailOTP3.0.26 – 3.0.26.16
- WSO2 / WSO2 Carbon Authenticator Library For EmailOTP3.0.5 – 3.0.5.8
- WSO2 / WSO2 Identity Server0 – 5.10.0
- WSO2 / WSO2 Identity Server5.10.0 – 5.10.0.379
- WSO2 / WSO2 Identity Server5.11.0 – 5.11.0.426
- WSO2 / WSO2 Identity Server5.11.0 – 5.11.0.431
- WSO2 / WSO2 Identity Server6.0.0 – 6.0.0.253
- WSO2 / WSO2 Identity Server6.1.0 – 6.1.0.254
- WSO2 / WSO2 Identity Server7.0.0 – 7.0.0.131
- WSO2 / WSO2 Identity Server as Key Manager5.10.0 – 5.10.0.267
- WSO2 / WSO2 Identity Server as Key Manager0 – 5.10.0
- WSO2 / WSO2 Open Banking IAM2.0.0 – 2.0.0.318
- WSO2 / WSO2 Open Banking IAM0 – 2.0.0