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 |
Configurations
Configuration 1 (hide)
|
History
No history.
Information
Published : 2019-08-28 21:15
Updated : 2024-02-04 20:20
NVD link : CVE-2019-10056
Mitre link : CVE-2019-10056
CVE.ORG link : CVE-2019-10056
JSON object : View
Products Affected
suricata-ids
- suricata
CWE
CWE-787
Out-of-bounds Write