Executive Summary
Summary | |
---|---|
Title | Radware Cloud Web Application Firewall Vulnerable to Filter Bypass |
Informations | |||
---|---|---|---|
Name | VU#722229 | First vendor Publication | 2025-05-07 |
Vendor | VU-CERT | Last vendor Modification | 2025-06-11 |
Severity (Vendor) | N/A | Revision | M |
Security-Database Scoring CVSS v3
Cvss vector : N/A | |||
---|---|---|---|
Overall CVSS Score | NA | ||
Base Score | NA | Environmental Score | NA |
impact SubScore | NA | Temporal Score | NA |
Exploitabality Sub Score | NA | ||
Calculate full CVSS 3.0 Vectors scores |
Security-Database Scoring CVSS v2
Cvss vector : | |||
---|---|---|---|
Cvss Base Score | N/A | Attack Range | N/A |
Cvss Impact Score | N/A | Attack Complexity | N/A |
Cvss Expoit Score | N/A | Authentication | N/A |
Calculate full CVSS 2.0 Vectors scores |
Detail
OverviewThe Radware Cloud Web Application Firewall is vulnerable to filter bypass by multiple means. The first is via specially crafted HTTP request and the second being insufficient validation of user-supplied input when processing a special character. An attacker with knowledge of these vulnerabilities can perform additional attacks without interference from the firewall. DescriptionThe Radware Cloud Web Application Firewall can be bypassed by means of a crafted HTTP request. If random data is included in the HTTP request body with a HTTP GET method, WAF protections may be bypassed. It should be noted that this evasion is only possible for those requests that use the HTTP GET method. Another way the Radware Cloud WAF can be bypassed is if an attacker adds a special character to the request. The firewall fails to filter these requests and allows for various payloads to reach the underlying web application. ImpactAn attacker with knowledge of these vulnerabilities can bypass filtering. This allows malicious inputs to reach the underlying web application. SolutionThe vulnerabilities appear to be fixed (see reference URL below). Initially Radware did not acknowledge the reporter's findings when they were first disclosed. As of June 4, 2025, Radware has reached out to the SEI and has stated that Radware acknowledges the vulnerability and appreciates the responsible disclosure. Additionally, Radware has fixed the issue and published a technical knowledge base article covering the CVE and attributing the discovery to Oriol Gegundez. AcknowledgementsThanks to Oriol Gegundez for reporting this issue. This document was written by Kevin Stephens and Ben Koo. |
Original Source
Url : https://kb.cert.org/vuls/id/722229 |
Alert History
Date | Informations |
---|---|
2025-06-12 05:34:25 |
|
2025-06-12 05:20:26 |
|
2025-05-31 00:33:28 |
|
2025-05-31 00:20:22 |
|
2025-05-27 21:33:16 |
|
2025-05-27 21:20:22 |
|
2025-05-26 21:20:24 |
|