Denial of Service via Malicious JSON Payloads in Throttling Events in Multiple WSO2 Products Causing Persistent Service Disruption
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.5.0.54, 4.6.0.18, 4.7.0.2, 4.5.0.53, 4.5.0.55, and 8 more
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
The throttling event handling mechanism in multiple WSO2 products accepts user-supplied JSON payloads without sufficient validation of their structure and content. This allows an unauthenticated remote attacker to inject malicious JSON data that can lead to a persistent denial of service condition. Successful exploitation of this vulnerability can disrupt the API Gateway, preventing legitimate API traffic from being processed and impacting complete service availability. The denial of service is persistent, requiring manual intervention to restore normal operations.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- WSO2 WSO2 Universal Gateway
From 4.5.0 · fixed in 4.5.0.54; From 4.6.0 · fixed in 4.6.0.18; From 4.7.0 · fixed in 4.7.0.2
- WSO2 WSO2 Traffic Manager
From 4.5.0 · fixed in 4.5.0.53; From 4.6.0 · fixed in 4.6.0.18; From 4.7.0 · fixed in 4.7.0.2
- WSO2 WSO2 API Control Plane
From 4.5.0 · fixed in 4.5.0.55; From 4.6.0 · fixed in 4.6.0.19; From 4.7.0 · fixed in 4.7.0.2
- WSO2 WSO2 API Manager
From 3.2.0 · fixed in 3.2.0.470; From 3.2.1 · fixed in 3.2.1.89; From 4.0.0 · fixed in 4.0.0.390; From 4.1.0 · fixed in 4.1.0.254; From 4.2.0 · fixed in 4.2.0.194; From 4.3.0 · fixed in 4.3.0.105; From 4.4.0 · fixed in 4.4.0.69; From 4.5.0 · fixed in 4.5.0.54; From 4.6.0 · fixed in 4.6.0.18; From 4.7.0 · fixed in 4.7.0.2