Authentication Bypass in Multiple WSO2 Products via Stale FIDO Credential Association
No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in Identity Server 5.10.0.338, Identity Server 5.10.0.345, Identity Server 5.11.0.394 and 1 more.
An authentication bypass vulnerability exists in multiple WSO2 products when FIDO authentication is enabled. When a user account is deleted, the system does not automatically remove associated FIDO registration data. If a new user account is later created using the same username, the system may associate the new account with the previously registered FIDO device. This flaw may allow a previously deleted user to authenticate using their FIDO credentials and impersonate the newly created user, resulting in unauthorized access. The vulnerability applies only to deployments that utilize FIDO-based authentication.
Affected
Vendors, products and packages with version ranges
| Vendor | Product | Versions | Fixed |
|---|---|---|---|
| WSO2 | Identity Server | >=5.10.0 <5.10.0.338, >=5.10.0 <5.10.0.345, >=5.11.0 <5.11.0.394 | 5.10.0.338, 5.10.0.345, 5.11.0.394 |
| WSO2 | Open Banking IAM | >=2.0.0 <2.0.0.389 | 2.0.0.389 |
Timeline
Every event on this vulnerability
Related
Other vulnerabilities in WSO2, strongest first
Embed
A live severity badge for an advisory, README or ticket