Page 4 of 25 results (0.000 seconds)

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 1

Open Information Security Foundation Suricata prior to version 4.1.3 is affected by: Denial of Service - TCP/HTTP detection bypass. The impact is: An attacker can evade a signature detection with a specialy formed sequence of network packets. The component is: detect.c (https://github.com/OISF/suricata/pull/3625/commits/d8634daf74c882356659addb65fb142b738a186b). The attack vector is: An attacker can trigger the vulnerability by a specifically crafted network TCP session. The fixed version is: 4.1.3. • https://github.com/OISF/suricata/pull/3625 https://github.com/OISF/suricata/pull/3625/commits/d8634daf74c882356659addb65fb142b738a186b https://redmine.openinfosecfoundation.org/issues/2770 • CWE-347: Improper Verification of Cryptographic Signature •

CVSS: 5.3EPSS: 0%CPEs: 1EXPL: 1

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. Se ha descubierto un problema en versiones anteriores a la 3.1.2 de Suricata. • https://github.com/kirillwow/ids_bypass https://lists.debian.org/debian-lts-announce/2018/09/msg00019.html https://redmine.openinfosecfoundation.org/issues/1880 https://suricata-ids.org/2016/09/07/suricata-3-1-2-released • CWE-20: Improper Input Validation •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 2

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). Suricata en versiones anteriores a la 4.0.5 detiene la inspección de transmisiones TCP al recibir un TCP RST de un servidor. Esto permite la omisión de la detección debido a que los clientes de Windows TCP continuaban el procesamiento habitual de datos TCP que llegan poco después de un RST (por ejemplo, actúan como si el RST no se hubiese recibido aún). • https://github.com/OISF/suricata/pull/3428/commits/843d0b7a10bb45627f94764a6c5d468a24143345 https://github.com/kirillwow/ids_bypass https://redmine.openinfosecfoundation.org/issues/2501 https://suricata-ids.org/2018/07/18/suricata-4-0-5-available •

CVSS: 5.3EPSS: 59%CPEs: 2EXPL: 1

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 signatures. This mostly affects IDS signatures for the HTTP protocol and TCP stream content; signatures for TCP packets will inspect such network traffic as usual. Suricata en versiones anteriores a la 4.0.4 es propenso a una vulnerabilidad de omisión de detección HTTP en detect.c y stream-tcp.c. Si un servidor malicioso interrumpe un flujo TCP normal y envía datos antes de que se complete el handshake tridireccional, los datos enviados por el servidor malicioso se aceptarán por parte de clientes web como el navegador web o herramientas de interfaz de línea de comandos de Linux, pero las firmas IDS de Suricata los ignorarán. • https://www.exploit-db.com/exploits/44247 https://github.com/OISF/suricata/pull/3202/commits/e1ef57c848bbe4e567d5d4b66d346a742e3f77a1 https://lists.debian.org/debian-lts-announce/2018/12/msg00000.html https://redmine.openinfosecfoundation.org/issues/2427 https://suricata-ids.org/2018/02/14/suricata-4-0-4-available • CWE-693: Protection Mechanism Failure •

CVSS: 7.5EPSS: 0%CPEs: 1EXPL: 0

In Suricata before 4.x, it was possible to trigger lots of redundant checks on the content of crafted network traffic with a certain signature, because of DetectEngineContentInspection in detect-engine-content-inspection.c. The search engine doesn't stop when it should after no match is found; instead, it stops only upon reaching inspection-recursion-limit (3000 by default). En Suricata en versiones anteriores a las 4.x, era posible desencadenar numerosos chequeos redundantes en el contenido del trafico de red manipulado con una firma especifica a causa de DetectEngineContentInspection en detect-engine-content-inspection.c. El motor de busqueda no se detiene cuando deberí­a despues de que no se encuentre ninguna coincidencia. En su lugar, solo se detiene al llegar al lí­mite de recursión de inspecciónn (3000 por defecto). • https://github.com/OISF/suricata/commit/b9579fbe7dd408200ef03cbe20efddb624b73885 https://lists.debian.org/debian-lts-announce/2018/12/msg00000.html https://redmine.openinfosecfoundation.org/issues/2231 •