Suricata-ids
Suricata-ids Suricata: vulnerabilities and CVEs
Suricata-ids Suricata has 14 published vulnerabilities, 0 of them in the last 12 months. 4 are rated critical and 0 are listed by CISA as actively exploited.
CVEs14
Last 12 months0
Critical4
Actively exploited0
All vulnerabilities in the catalogue →⭐ Follow this technology
Latest vulnerabilities
| CVE | Severity | EPSS | Active exploitation | Published | Description |
|---|---|---|---|---|---|
| CVE-2019-17420 | Medium (5.3) | 1.4% | — | Oct 10, 2019 | In OISF LibHTP before 0.5.31, as used in Suricata 4.1.4 and other products, an HTTP protocol parsing error causes the http_header signature to not alert on a response with a single \r\n ending. |
| CVE-2019-16411 | Critical (9.8) | 2.0% | — | Sep 24, 2019 | An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated.… |
| CVE-2019-16410 | Critical (9.1) | 2.1% | — | Sep 24, 2019 | An issue was discovered in Suricata 4.1.4. By sending multiple fragmented IPv4 packets, the function Defrag4Reassemble in defrag.c tries to access a memory region that is not allocated, because of a lack of header_len… |
| CVE-2019-15699 | Critical (9.1) | 1.6% | — | Sep 24, 2019 | An issue was discovered in app-layer-ssl.c in Suricata 4.1.4. Upon receiving a corrupted SSLv3 (TLS 1.2) packet, the parser function TLSDecodeHSHelloExtensions tries to access a memory region that is not allocated,… |
| CVE-2019-10056 | High (7.5) | 1.4% | — | Aug 28, 2019 | An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet with the right type, such that the function DecodeEthernet in decode-ethernet.c is executed a second time. At this… |
| CVE-2019-10055 | High (7.5) | 1.5% | — | Aug 28, 2019 | An issue was discovered in Suricata 4.1.3. The function ftp_pasv_response lacks a check for the length of part1 and part2, leading to a crash within the ftp/mod.rs file. |
| CVE-2019-10054 | High (7.5) | 1.4% | — | Aug 28, 2019 | An issue was discovered in Suricata 4.1.3. The function process_reply_record_v3 lacks a check for the length of reply.data. It causes an invalid memory access and the program crashes within the nfs/nfs3.rs file. |
| CVE-2019-10052 | High (7.5) | 2.1% | — | Aug 28, 2019 | An issue was discovered in Suricata 4.1.3. If the network packet does not have the right length, the parser tries to access a part of a DHCP packet. At this point, the Rust environment runs into a panic in… |
| CVE-2019-10051 | High (7.5) | 2.1% | — | Aug 28, 2019 | An issue was discovered in Suricata 4.1.3. If the function filetracker_newchunk encounters an unsafe "Some(sfcm) => { ft.new_chunk }" item, then the program enters an smb/files.rs error condition and crashes. |
| CVE-2019-10053 | Critical (9.8) | 1.7% | — | May 13, 2019 | An issue was discovered in Suricata 4.1.x before 4.1.4. If the input of the function SSHParseBanner is composed only of a \n character, then the program runs into a heap-based buffer over-read. This occurs because the… |
| CVE-2018-18956 | High (7.5) | 2.8% | — | Nov 5, 2018 | The ProcessMimeEntity function in util-decode-mime.c in Suricata 4.x before 4.0.6 allows remote attackers to cause a denial of service (segfault and daemon crash) via crafted input to the SMTP parser, as exploited in… |
| CVE-2018-14568 | High (7.5) | 2.0% | — | Jul 23, 2018 | Suricata before 4.0.5 stops TCP stream inspection upon a TCP RST from a server. This allows detection bypass because Windows TCP clients proceed with normal processing of TCP data that arrives shortly after an RST… |
| CVE-2016-10728 | Medium (5.3) | 2.1% | — | Jul 23, 2018 | An issue was discovered in Suricata before 3.1.2. If an ICMPv4 error packet is received as the first packet on a flow in the to_client direction, it confuses the rule grouping lookup logic. The toclient inspection will… |
| CVE-2018-6794 | Medium (5.3) | 24% | — | Feb 7, 2018 | Suricata before 4.0.4 is prone to an HTTP detection bypass vulnerability in detect.c and stream-tcp.c. If a malicious server breaks a normal TCP flow and sends data before the 3-way handshake is complete, then the data… |