An issue was discovered in Suricata before 6.0.4. It is possible to bypass/evade any HTTP-based signature by faking an RST TCP packet with random TCP options of the md5header from the client side. After the three-way handshake, it's possible to inject an RST ACK with a random TCP md5header option. Then, the client can send an HTTP GET request with a forbidden URL. The server will ignore the RST ACK and send the response HTTP packet for the client's request. These packets will not trigger a Suricata reject action.
Metrics
Affected Vendors & Products
References
History
No history.
MITRE
Status: PUBLISHED
Assigner: mitre
Published: 2021-12-16T04:07:57
Updated: 2024-08-04T04:32:13.665Z
Reserved: 2021-12-16T00:00:00
Link: CVE-2021-45098
Vulnrichment
No data.
NVD
Status : Analyzed
Published: 2021-12-16T05:15:08.727
Modified: 2022-01-04T16:48:54.087
Link: CVE-2021-45098
Redhat
No data.