Vulnerability Description
An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that is not allocated. There is a check for o->len < 5 (corresponding to 2 bytes of header and 3 bytes of data). Then, "flag = *(o->data + 3)" places one beyond the 3 bytes, because the code should have been "flag = *(o->data + 1)" instead.
CVSS Score
CRITICAL
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Suricata-Ids | Suricata | 4.1.4 |
Related Weaknesses (CWE)
References
- https://lists.openinfosecfoundation.org/pipermail/oisf-announce/Third Party Advisory
- https://suricata-ids.org/2019/09/24/suricata-4-1-5-released/Release NotesVendor Advisory
- https://www.code-intelligence.com/cve-2019-16411
- https://lists.openinfosecfoundation.org/pipermail/oisf-announce/Third Party Advisory
- https://suricata-ids.org/2019/09/24/suricata-4-1-5-released/Release NotesVendor Advisory
- https://www.code-intelligence.com/cve-2019-16411
FAQ
What is CVE-2019-16411?
CVE-2019-16411 is a vulnerability with a CVSS score of 9.8 (CRITICAL). An issue was discovered in Suricata 4.1.4. By sending multiple IPv4 packets that have invalid IPv4Options, the function IPV4OptValidateTimestamp in decode-ipv4.c tries to access a memory region that i...
How severe is CVE-2019-16411?
CVE-2019-16411 has been rated CRITICAL with a CVSS base score of 9.8/10. This is considered a critical vulnerability requiring immediate attention.
Is there a patch for CVE-2019-16411?
Check the references section above for vendor advisories and patch information. Affected products include: Suricata-Ids Suricata.