CVE-2019-16411
First published: Tue Sep 24 2019(Updated: )
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.
Credit: cve@mitre.org
| Affected Software | Affected Version | How to fix |
|---|---|---|
| Suricata-ids Suricata | =4.1.4 |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is CVE-2019-16411?
CVE-2019-16411 is a vulnerability in Suricata 4.1.4 that allows an attacker to access an unallocated memory region by sending multiple IPv4 packets with invalid IPv4Options.
What is the severity of CVE-2019-16411?
CVE-2019-16411 has a severity rating of critical with a score of 9.8.
How can an attacker exploit CVE-2019-16411?
An attacker can exploit CVE-2019-16411 by sending multiple IPv4 packets with invalid IPv4Options, which triggers an attempt to access an unallocated memory region.
Is there a fix available for CVE-2019-16411?
Yes, a fix for CVE-2019-16411 is available in Suricata version 4.1.5.
Where can I find more information about CVE-2019-16411?
You can find more information about CVE-2019-16411 on the official Suricata website and the Code Intelligence website.
- collector/nvd-index
- agent/weakness
- agent/author
- agent/severity
- agent/references
- agent/tags
- agent/description
- agent/type
- agent/event
- agent/last-modified-date
- agent/softwarecombine
- agent/first-publish-date
- collector/mitre-cve
- source/MITRE
- vendor/suricata-ids
- canonical/suricata-ids suricata
- version/suricata-ids suricata/4.1.4