Suricata-Ids Suricata vulnerabilities

CVE-2019-17420 [MEDIUM] CWE-459 CVE-2019-17420: In OISF LibHTP before 0.5.31, as used in Suricata 4.1.4 and other products, an HTTP protocol parsing 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-15699 [CRITICAL] CWE-125 CVE-2019-15699: An issue was discovered in app-layer-ssl.c in Suricata 4.1.4. Upon receiving a corrupted SSLv3 (TLS 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, because the expected length of HSHelloExtensions does not match the real length of the HSHelloExtensions part of the packet.

CVE-2019-16410 [CRITICAL] CWE-125 CVE-2019-16410: An issue was discovered in Suricata 4.1.4. By sending multiple fragmented IPv4 packets, the function 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 checking.

CVE-2019-16411 [CRITICAL] CWE-125 CVE-2019-16411: An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Op 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. There is a check for o->len data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" inst

CVE-2019-10052 [HIGH] CWE-707 CVE-2019-10052: An issue was discovered in Suricata 4.1.3. If the network packet does not have the right length, the 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 parse_clientid_option in the dhcp/parser.rs file.

CVE-2019-10054 [HIGH] CWE-20 CVE-2019-10054: An issue was discovered in Suricata 4.1.3. The function process_reply_record_v3 lacks a check for th 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-10055 [HIGH] CWE-190 CVE-2019-10055: An issue was discovered in Suricata 4.1.3. The function ftp_pasv_response lacks a check for the leng 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-10056 [HIGH] CWE-787 CVE-2019-10056: An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet 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 point, the algorithm cuts the first part of the packet and doesn't determine the current length. Specifically, if the packet is exactly 28

CVE-2019-10051 [HIGH] CWE-754 CVE-2019-10051: An issue was discovered in Suricata 4.1.3. If the function filetracker_newchunk encounters an unsafe 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] CWE-125 CVE-2019-10053: An issue was discovered in Suricata 4.1.x before 4.1.4. If the input of the function SSHParseBanner 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 erroneous search for \r results in an integer underflow.

CVE-2018-18956 [HIGH] CWE-119 CVE-2018-18956: The ProcessMimeEntity function in util-decode-mime.c in Suricata 4.x before 4.0.6 allows remote atta 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 the wild in November 2018.

CVE-2018-14568 [HIGH] CVE-2018-14568: Suricata before 4.0.5 stops TCP stream inspection upon a TCP RST from a server. This allows detectio 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 (i.e., they act as if the RST had not yet been received).

CVE-2016-10728 [MEDIUM] CWE-20 CVE-2016-10728: An issue was discovered in Suricata before 3.1.2. If an ICMPv4 error packet is received as the first 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 then continue with the wrong rule group. This can lead to missed detection.

CVE-2018-6794 [MEDIUM] CWE-693 CVE-2018-6794: Suricata before 4.0.4 is prone to an HTTP detection bypass vulnerability in detect.c and stream-tcp. 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 sent by the malicious server will be accepted by web clients such as a web browser or Linux CLI utilities, but ignored by Suricata IDS