CVE-2019-10056
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.
Does this matter?
High impact if exploited, but EPSS currently rates exploitation as unlikely (1.40%). Schedule it in the normal patch cycle and watch for a rise in EPSS or a public exploit.
Description
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.
- CVSS 3.0
- 7.5 HIGHCVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
- EPSS
- 1.40% probability · 71th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-787
- Affected
- suricata-ids/suricata
- Source
- cve@mitre.org
References
- https://redmine.openinfosecfoundation.org/issues/2946Exploit, Issue Tracking, Third Party Advisory
- https://suricata-ids.org/2019/04/30/suricata-4-1-4-released/Not Applicable, Release Notes, Vendor Advisory
- https://redmine.openinfosecfoundation.org/issues/2946Exploit, Issue Tracking, Third Party Advisory
- https://suricata-ids.org/2019/04/30/suricata-4-1-4-released/Not Applicable, Release Notes, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.