CVE-2017-15377: High severity Openinfosecfoundation Suricata vulnerability
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).
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2017-15377?
CVE-2017-15377 is considered a medium severity vulnerability that can lead to inefficient processing of crafted network traffic.
How do I fix CVE-2017-15377?
To fix CVE-2017-15377, upgrade Suricata to version 4.x or later.
What versions of Suricata are affected by CVE-2017-15377?
Suricata versions before 4.x, specifically up to and including 3.2.4, are affected by CVE-2017-15377.
What are the consequences of exploiting CVE-2017-15377?
Exploiting CVE-2017-15377 can lead to performance degradation due to redundant checks on network traffic.
Is CVE-2017-15377 a denial of service vulnerability?
CVE-2017-15377 can potentially lead to a denial of service condition through excessive resource consumption.