CVE-2019-18792
published 2020-01-06CVE-2019-18792: An issue was discovered in Suricata 5.0.0. It is possible to bypass/evade any tcp based signature by overlapping a TCP segment with a fake FIN packet. The fake…
PriorityP349critical9.1CVSS 3.1
AVNACLPRNUINSUCNIHAH
EPSS
2.52%
82.9th percentile
An issue was discovered in Suricata 5.0.0. It is possible to bypass/evade any tcp based signature by overlapping a TCP segment with a fake FIN packet. The fake FIN packet is injected just before the PUSH ACK packet we want to bypass. The PUSH ACK packet (containing the data) will be ignored by Suricata because it overlaps the FIN packet (the sequence and ack number are identical in the two packets). The client will ignore the fake FIN packet because the ACK flag is not set. Both linux and windows clients are ignoring the injected packet.
Affected
8 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | debian_linux | — | — |
| debian | suricata | < suricata 1:5.0.2-1 (bookworm) | suricata 1:5.0.2-1 (bookworm) |
| oisf | suricata | — | — |
| oisf | suricata | >= 0 < 1:5.0.2-1 | 1:5.0.2-1 |
| oisf | suricata | >= 0 < 1:5.0.2-1 | 1:5.0.2-1 |
| oisf | suricata | >= 0 < 1:5.0.2-1 | 1:5.0.2-1 |
| oisf | suricata | >= 0 < 1:5.0.2-1 | 1:5.0.2-1 |
| oisf | suricata | >= 4.1.5 < 4.1.6 | 4.1.6 |
CVSS provenance
nvdv3.19.1CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
nvdv2.06.4MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:P
osv9.1CRITICAL
vendor_debian9.1CRITICAL
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
Debian
CVE-2019-18792: suricata - An issue was discovered in Suricata 5.0.0. It is possible to bypass/evade any tc...
vendor_debian·2019·CVSS 9.1
CVE-2019-18792 [CRITICAL] CVE-2019-18792: suricata - An issue was discovered in Suricata 5.0.0. It is possible to bypass/evade any tc...
An issue was discovered in Suricata 5.0.0. It is possible to bypass/evade any tcp based signature by overlapping a TCP segment with a fake FIN packet. The fake FIN packet is injected just before the PUSH ACK packet we want to bypass. The PUSH ACK packet (containing the data) will be ignored by Suricata because it overlaps the FIN packet (the sequence and ack number are identical in the two packets). The client will ignore the fake FIN packet because the ACK flag is not set. Both linux and windows clients are ignoring the injected packet.
Scope: local
bookworm: resolved (fixed in 1:5.0.2-1)
bullseye: resolved (fixed in 1:5.0.2-1)
forky: resolved (fixed in 1:5.0.2-1)
sid: resolved (fixed in 1:5.0.2-1)
trixie: resolved (fixed in 1:5.0.2-1)
GHSA
GHSA-p4hg-mvq8-47jj: An issue was discovered in Suricata 5
ghsa_unreviewed·2022-05-24
CVE-2019-18792 [MEDIUM] CWE-436 GHSA-p4hg-mvq8-47jj: An issue was discovered in Suricata 5
An issue was discovered in Suricata 5.0.0. It is possible to bypass/evade any tcp based signature by overlapping a TCP segment with a fake FIN packet. The fake FIN packet is injected just before the PUSH ACK packet we want to bypass. The PUSH ACK packet (containing the data) will be ignored by Suricata because it overlaps the FIN packet (the sequence and ack number are identical in the two packets). The client will ignore the fake FIN packet because the ACK flag is not set. Both linux and windows clients are ignoring the injected packet.
OSV
CVE-2019-18792: An issue was discovered in Suricata 5
osv·2020-01-06·CVSS 9.1
CVE-2019-18792 [CRITICAL] CVE-2019-18792: An issue was discovered in Suricata 5
An issue was discovered in Suricata 5.0.0. It is possible to bypass/evade any tcp based signature by overlapping a TCP segment with a fake FIN packet. The fake FIN packet is injected just before the PUSH ACK packet we want to bypass. The PUSH ACK packet (containing the data) will be ignored by Suricata because it overlaps the FIN packet (the sequence and ack number are identical in the two packets). The client will ignore the fake FIN packet because the ACK flag is not set. Both linux and windows clients are ignoring the injected packet.
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
https://github.com/OISF/suricata/commit/1c63d3905852f746ccde7e2585600b2199cefb4bhttps://github.com/OISF/suricata/commit/fa692df37a796c3330c81988d15ef1a219afc006https://lists.debian.org/debian-lts-announce/2020/01/msg00032.htmlhttps://redmine.openinfosecfoundation.org/issues/3324https://redmine.openinfosecfoundation.org/issues/3394https://github.com/OISF/suricata/commit/1c63d3905852f746ccde7e2585600b2199cefb4bhttps://github.com/OISF/suricata/commit/fa692df37a796c3330c81988d15ef1a219afc006https://lists.debian.org/debian-lts-announce/2020/01/msg00032.htmlhttps://redmine.openinfosecfoundation.org/issues/3324https://redmine.openinfosecfoundation.org/issues/3394
2020-01-06
Published