CVE-2019-10056
published 2019-08-28CVE-2019-10056: An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet with the right type, such that the function DecodeEthernet…
PriorityP336high7.5CVSS 3.0
AVNACLPRNUINSUCNINAH
EPSS
1.40%
69.1th percentile
An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet with the right type, such that the function DecodeEthernet in decode-ethernet.c is executed a second time. At this point, the algorithm cuts the first part of the packet and doesn't determine the current length. Specifically, if the packet is exactly 28 long, in the first iteration it subtracts 14 bytes. Then, it is working with a packet length of 14. At this point, the case distinction says it is a valid packet. After that it casts the packet, but this packet has no type, and the program crashes at the type case distinction.
Affected
7 ranges
| Vendor | Product | Version range | Fixed in |
|---|---|---|---|
| debian | suricata | < suricata 1:4.1.4-1 (bookworm) | suricata 1:4.1.4-1 (bookworm) |
| oisf | suricata | >= 0 < 1:4.1.4-1 | 1:4.1.4-1 |
| oisf | suricata | >= 0 < 1:4.1.4-1 | 1:4.1.4-1 |
| oisf | suricata | >= 0 < 1:4.1.4-1 | 1:4.1.4-1 |
| oisf | suricata | >= 0 < 1:4.1.4-1 | 1:4.1.4-1 |
| suricata-ids | suricata | — | — |
| suricata-ids | suricata | — | — |
CVSS provenance
nvdv3.07.5HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
nvdv2.05.0MEDIUMAV:N/AC:L/Au:N/C:N/I:N/A:P
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.
Debian
CVE-2019-10056: suricata - An issue was discovered in Suricata 4.1.3. The code mishandles the case of sendi...
vendor_debian·2019·CVSS 7.5
CVE-2019-10056 [HIGH] CVE-2019-10056: suricata - An issue was discovered in Suricata 4.1.3. The code mishandles the case of sendi...
An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet with the right type, such that the function DecodeEthernet in decode-ethernet.c is executed a second time. At this point, the algorithm cuts the first part of the packet and doesn't determine the current length. Specifically, if the packet is exactly 28 long, in the first iteration it subtracts 14 bytes. Then, it is working with a packet length of 14. At this point, the case distinction says it is a valid packet. After that it casts the packet, but this packet has no type, and the program crashes at the type case distinction.
Scope: local
bookworm: resolved (fixed in 1:4.1.4-1)
bullseye: resolved (fixed in 1:4.1.4-1)
forky: resolved (fixed in 1:4.1.4-1)
sid: resolved (fixed in 1:4.1.4-1)
tri
GHSA
GHSA-fh58-6cxc-xhx5: An issue was discovered in Suricata 4
ghsa_unreviewed·2022-05-24
CVE-2019-10056 [HIGH] CWE-119 GHSA-fh58-6cxc-xhx5: An issue was discovered in Suricata 4
An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet with the right type, such that the function DecodeEthernet in decode-ethernet.c is executed a second time. At this point, the algorithm cuts the first part of the packet and doesn't determine the current length. Specifically, if the packet is exactly 28 long, in the first iteration it subtracts 14 bytes. Then, it is working with a packet length of 14. At this point, the case distinction says it is a valid packet. After that it casts the packet, but this packet has no type, and the program crashes at the type case distinction.
OSV
CVE-2019-10056: An issue was discovered in Suricata 4
osv·2019-08-28·CVSS 7.5
CVE-2019-10056 [HIGH] CVE-2019-10056: An issue was discovered in Suricata 4
An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet with the right type, such that the function DecodeEthernet in decode-ethernet.c is executed a second time. At this point, the algorithm cuts the first part of the packet and doesn't determine the current length. Specifically, if the packet is exactly 28 long, in the first iteration it subtracts 14 bytes. Then, it is working with a packet length of 14. At this point, the case distinction says it is a valid packet. After that it casts the packet, but this packet has no type, and the program crashes at the type case distinction.
No detection rules found.
No public exploits indexed.
2019-08-28
Published