Skip to content
Fencer Vulns
medium 5.3

CVE-2018-6794 json

Suricata before 4.0.4 is prone to an HTTP detection bypass vulnerability in detect.c and stream-tcp.c.

published 2018-02-07 8 y ago modified 2026-06-17 4 mo ago also EUVD-2018-18541

cvss
5.3
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
23.7%
EPSS 23.7% chance of exploitation in 30 days, percentile 97%
public exploits
1
Exploit-DB

Summary

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.

Patch / fix

  • suricata-ids suricata 4.0.4
  • suricata Debian 14, Debian 13 1:4.0.4-1

debian advisories DEBIAN-CVE-2018-6794

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2018-6794 updated cvss 5.5

suricata: HTTP detection bypass in detect.c and stream-tcp.c

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. Published
  2. First public exploit (EDB-44247)

Exploit prediction

23.69% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-44247 Suricata < 4.0.4 - IDS Detection Bypass dos, 2018-03-05

CVSS scores

assigned by version score vector
NVD 3.0 5.3 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-693 Protection Mechanism Failure

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.