How severe is CVE-2019-16411?

CVE-2019-16411 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2019-16411 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2019-16411?

CVE-2019-16411 affects Suricata-ids Suricata. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2019-16411?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2019-16411 published?

CVE-2019-16411 was published on 2019-09-24 and last updated on 2026-06-17.

CVE-2019-16411

CVE-2019-16411 is a critical-severity vulnerability in Suricata-ids Suricata with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-125.

Key facts

Severity: Critical (CVSS 3.x base score 9.8)
CVSS v2: 7.5
EPSS exploit prediction: 2% (79th percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-125
Affected product: Suricata-ids Suricata
Published: 2019-09-24
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2019-16411?: 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.
How severe is CVE-2019-16411?: CVE-2019-16411 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2019-16411 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (79th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2019-16411?: CVE-2019-16411 affects Suricata-ids Suricata. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2019-16411?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2019-16411 published?: CVE-2019-16411 was published on 2019-09-24 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:suricata-ids:suricata:4.1.4:*:*:*:*:*:*:*

More vulnerabilities in Suricata-ids Suricata

CVE-2019-10053 — Critical (CVSS 9.8): An issue was discovered in Suricata 4.1.x before 4.1.4. If the input of the function SSHParseBanner is composed only of…
CVE-2019-16410 — Critical (CVSS 9.1): An issue was discovered in Suricata 4.1.4. By sending multiple fragmented IPv4 packets, the function Defrag4Reassemble…
CVE-2019-15699 — Critical (CVSS 9.1): An issue was discovered in app-layer-ssl.c in Suricata 4.1.4. Upon receiving a corrupted SSLv3 (TLS 1.2) packet, the…
CVE-2019-10056 — High (CVSS 7.5): An issue was discovered in Suricata 4.1.3. The code mishandles the case of sending a network packet with the right…
CVE-2019-10055 — High (CVSS 7.5): An issue was discovered in Suricata 4.1.3. The function ftp_pasv_response lacks a check for the length of part1 and…
CVE-2019-10054 — High (CVSS 7.5): An issue was discovered in Suricata 4.1.3. The function process_reply_record_v3 lacks a check for the length of…

All CVEs affecting Suricata-ids Suricata →

Other CWE-125 (Out-of-bounds Read) vulnerabilities

CVE-2026-24826 — Critical (CVSS 10.0): Out-of-bounds Write, Divide By Zero, NULL Pointer Dereference, Use of Uninitialized Resource, Out-of-bounds Read,…
CVE-2024-22004 — Critical (CVSS 10.0): Due to length check, an attacker with privilege access on a Linux Nonsecure operating system can trigger a…
CVE-2021-41556 — Critical (CVSS 10.0): sqclass.cpp in Squirrel through 2.2.5 and 3.x through 3.1 allows an out-of-bounds read (in the core interpreter) that…
CVE-2021-21777 — Critical (CVSS 10.0): An information disclosure vulnerability exists in the Ethernet/IP UDP handler functionality of EIP Stack Group OpENer…
CVE-2017-14451 — Critical (CVSS 10.0): An exploitable out-of-bounds read vulnerability exists in libevm (Ethereum Virtual Machine) of CPP-Ethereum. A…
CVE-2013-0767 — Critical (CVSS 10.0): The nsSVGPathElement::GetPathLengthScale function in Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and…

Browse all CWE-125 (Out-of-bounds Read) vulnerabilities →