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.

Vulnerability/
CVE-2017-15377

high

7.5

23/10/2017

27/10/2020

CVE-2017-15377

First published: Mon Oct 23 2017(Updated: )

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

Credit: cve@mitre.org

Affected Software	Affected Version	How to fix
Suricata	<=3.2.4

Never miss a vulnerability like this again

Reference Links

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.

agent/type
agent/first-publish-date
agent/last-modified-date
agent/severity
agent/references
agent/author
agent/description
agent/event
agent/softwarecombine
agent/tags
collector/nvd-index
agent/software-canonical-lookup-request
vendor/openinfosecfoundation
canonical/suricata
version/suricata/3.2.4

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

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.