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.
References
Link | Resource |
---|---|
https://redmine.openinfosecfoundation.org/issues/2946 | Exploit Issue Tracking Third Party Advisory |
https://suricata-ids.org/2019/04/30/suricata-4-1-4-released/ | Not Applicable Release Notes Vendor Advisory |
History
No history.
MITRE Information
Status: PUBLISHED
Assigner: mitre
Published: 2019-08-28T20:17:17
Updated: 2019-08-28T20:17:17
Reserved: 2019-03-25T00:00:00
Link: CVE-2019-10056
JSON object: View
NVD Information
Status : Analyzed
Published: 2019-08-28T21:15:10.630
Modified: 2021-07-21T11:39:23.747
Link: CVE-2019-10056
JSON object: View
Redhat Information
No data.
CWE