CVE-2017-7177
published 2017-03-18CVE-2017-7177: Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack of a check for the IP protocol during fragment matching.
PriorityP433high7.5CVSS 3.0
AVNACLPRNUINSUCNIHAN
EPSS
1.26%
65.8th percentile
Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack of a check for the IP protocol during fragment matching.
Affected
6 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | suricata | < suricata 3.2.1-1 (bookworm) | suricata 3.2.1-1 (bookworm) |
| oisf | suricata | >= 0 < 3.2.1-1 | 3.2.1-1 |
| oisf | suricata | >= 0 < 3.2.1-1 | 3.2.1-1 |
| oisf | suricata | >= 0 < 3.2.1-1 | 3.2.1-1 |
| oisf | suricata | >= 0 < 3.2.1-1 | 3.2.1-1 |
| openinfosecfoundation | suricata | <= 3.2 | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:P/A:N
osv7.5HIGH
vendor_debian7.5HIGH
Stop checking back — get the weekly exploitation signal.
Every Monday: what got weaponized or added to CISA KEV in the last seven days — each CVE cross-linked to its PoC, Nuclei template, and detection rule. Free, one email a week, unsubscribe in one click.
GHSA
GHSA-9gxf-8qj8-9g4f: Suricata before 3
ghsa_unreviewed·2022-05-14
CVE-2017-7177 [HIGH] CWE-358 GHSA-9gxf-8qj8-9g4f: Suricata before 3
Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack of a check for the IP protocol during fragment matching.
OSV
CVE-2017-7177: Suricata before 3
osv·2017-03-18·CVSS 7.5
CVE-2017-7177 [HIGH] CVE-2017-7177: Suricata before 3
Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack of a check for the IP protocol during fragment matching.
Debian
CVE-2017-7177: suricata - Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack o...
vendor_debian·2017·CVSS 7.5
CVE-2017-7177 [HIGH] CVE-2017-7177: suricata - Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack o...
Suricata before 3.2.1 has an IPv4 defragmentation evasion issue caused by lack of a check for the IP protocol during fragment matching.
Scope: local
bookworm: resolved (fixed in 3.2.1-1)
bullseye: resolved (fixed in 3.2.1-1)
forky: resolved (fixed in 3.2.1-1)
sid: resolved (fixed in 3.2.1-1)
trixie: resolved (fixed in 3.2.1-1)
No detection rules found.
No public exploits indexed.
No writeups or analysis indexed.
http://www.securityfocus.com/bid/97047https://github.com/inliniac/suricata/commit/4a04f814b15762eb446a5ead4d69d021512df6f8https://lists.debian.org/debian-lts-announce/2018/12/msg00000.htmlhttps://redmine.openinfosecfoundation.org/issues/2019http://www.securityfocus.com/bid/97047https://github.com/inliniac/suricata/commit/4a04f814b15762eb446a5ead4d69d021512df6f8https://lists.debian.org/debian-lts-announce/2018/12/msg00000.htmlhttps://redmine.openinfosecfoundation.org/issues/2019
2017-03-18
Published