CVE-2017-7177

Suricata before versions 8.0.3 and 7.0.14 contains an unsigned integer overflow that can lead to a heap use-after-free condition when generating excessive amounts of alerts for a single packet. The issue is fixed in versions 8.0.3 and 7.0.14.

Suricata, a network IDS, IPS and NSM engine, can crash with a stack overflow. The vulnerability affects versions from 8.0.0 up to 8.0.2, and version 8.0.3 patches the issue.

Suricata before versions 8.0.3 and 7.0.14 has a vulnerability to excessive memory consumption while parsing DNP3 traffic. Specially crafted traffic can slow down the process and lead to memory exhaustion, potentially causing the process to be killed by the OOM killer.

Suricata before versions 8.0.3 and 7.0.14 has a vulnerability that allows crafted DCERPC traffic to cause unbounded buffer expansion, leading to memory exhaustion and process termination. The issue affects DCERPC over UDP and likely also over TCP and SMB. Patches are available in versions 8.0.3 and 7.0.14.

In Suricata before version 4.x, it was possible to trigger many redundant checks on the content of crafted network traffic due to a bug in DetectEngineContentInspection. The search engine did not stop when no match was found, leading to exceeding the inspection recursion limit.

In Suricata before version 6.0.13, an adversary controlling an external source of Lua rules may be able to execute Lua code. This issue is addressed in version 6.0.13 by disabling Lua unless the allow-rules option is set to true in the Lua security configuration section.

The MemcmpLowercase function in Suricata before version 2.0.6 improperly excludes the first byte from comparisons, which might allow remote attackers to bypass intrusion-prevention functionality via a crafted HTTP request.

A vulnerability in the suricata package for openSUSE Tumbleweed allows the suricata user to escalate privileges to root by following a UNIX symbolic link.

In Suricata before version 6.0.13, an adversary controlling an external source of rules may exploit a dataset filename to trigger directory traversal, leading to write access to the local filesystem. This issue is addressed in version 6.0.13 by requiring the use of allow-absolute-filenames and allow-write options in the datasets rules configuration section.