CVE-2017-15377

Description

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).

7.5

CVSS

Severity: High

CVSS 3.0 •

CVSS 2.0 •

EPSS 0.53%

Vendor Advisory openinfosecfoundation.org

Affected: n/a n/a

References

Link	Tags
https://lists.debian.org/debian-lts-announce/2018/12/msg00000.html	mailing list
https://redmine.openinfosecfoundation.org/issues/2231	vendor advisory
https://github.com/OISF/suricata/commit/b9579fbe7dd408200ef03cbe20efddb624b73885

Frequently Asked Questions

What is the severity of CVE-2017-15377?: CVE-2017-15377 has been scored as a high severity vulnerability.
How to fix CVE-2017-15377?: To fix CVE-2017-15377, make sure you are using an up-to-date version of the affected component(s) by checking the vendor release notes. As for now, there are no other specific guidelines available.
Is CVE-2017-15377 being actively exploited in the wild?: As for now, there are no information to confirm that CVE-2017-15377 is being actively exploited. According to its EPSS score, there is a ~1% probability that this vulnerability will be exploited by malicious actors in the next 30 days.

This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.