| Package | Affected versions | Patched versions |
|---|---|---|
| api control plane | = 4.5.0 | |
| api manager | = 2.2.0= 2.5.0= 2.6.0= 3.0.0= 3.1.0= 3.2.0= 3.2.1= 4.0.0= 4.1.0= 4.2.0= 4.3.0= 4.4.0= 4.5.0 | |
| identity server | = 5.10.0= 5.11.0= 5.2.0= 5.3.0= 5.4.0= 5.4.1= 5.5.0= 5.6.0= 5.7.0= 5.8.0= 5.9.0= 6.0.0= 6.1.0= 7.0.0= 7.1.0= 7.2.0 | |
| identity server as key manager | = 5.10.0= 5.3.0= 5.5.0= 5.6.0= 5.7.0= 5.9.0 | |
| open banking am | = 1.4.0= 1.5.0= 2.0.0 | |
| open banking iam | = 2.0.0 | |
| open banking km | = 1.4.0= 1.5.0 | |
| traffic manager | = 4.5.0 | |
| universal gateway | = 4.5.0 |
A missing authentication enforcement vulnerability exists in the mutual TLS (mTLS) implementation used by System REST APIs and SOAP services in multiple WSO2 products. Due to improper validation of client certificate–based authentication in certain default configurations, the affected components may permit unauthenticated requests even when mTLS is enabled. This condition occurs when relying on the default mTLS settings for System REST APIs or when the mTLS authenticator is enabled for SOAP services, causing these interfaces to accept requests without enforcing additional authentication. Successful exploitation allows a malicious actor with network access to the affected endpoints to gain administrative privileges and perform unauthorized operations. The vulnerability is exploitable only when the impacted mTLS flows are enabled and accessible in a given deployment. Other certificate-based authentication mechanisms such as Mutual TLS OAuth client authentication and X.509 login flows are not affected, and APIs served through the API Gateway of WSO2 API Manager remain unaffected.
Running one of these products? Scan your site to see whether it exposes a vulnerable version.
Scan my site free