WSO2 Universal Gateway vulnerability

What happened

The JWT authentication mechanism accepts tokens signed with algorithms other than those explicitly configured or supported. This allows an attacker to craft a JWT with an unsupported algorithm, which is then incorrectly validated, leading to unauthorized access. Successful exploitation of this vulnerability may result in unauthorized access to the system, including the potential compromise of administrative accounts and full account takeover. The CVSS score is adjusted to 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) in single-tenant deployments, reflecting that the impact is contained within a single security authority boundary.

Affected versions

WSO2 Universal Gateway: 4.5.0 through before 4.5.0.57 (custom); 4.6.0 through before 4.6.0.21 (custom); 4.5.0 through before 4.5.0.56 (custom); 4.5.0 through before 4.5.0.58 (custom); 4.6.0 through before 4.6.0.22 (custom); 4.1.0 through before 4.1.0.257 (custom); 4.2.0 through before 4.2.0.197 (custom); 4.3.0 through before 4.3.0.108 (custom); 4.4.0 through before 4.4.0.72 (custom); 9.20.74 through before 9.20.74.401 (custom); 9.28.116 through before 9.28.116.417 (custom); 9.29.120 through before 9.29.120.236 (custom); 9.30.67 through before 9.30.67.167 (custom); 9.31.86 through before 9.31.86.158 (custom); 9.32.147 through before 9.32.147.59 (custom) Fixed: See vendor advisory.

Why it matters

Review the vendor advisory and exposure of the affected product to determine operational impact.

Detection & mitigation

• Apply vendor-provided updates or mitigations.
• Review affected product exposure and access logs.