CVE-2019-16410

CRITICALNVD 9.19.1—

9.1

An issue was discovered in Suricata 4.1.4. By sending multiple fragmented IPv4 packets, the function Defrag4Reassemble in defrag.c tries to access a memory region that is not allocated, because of a lack of header_len checking.

CVSS v3: 9.1
EG Score: 9.1(medium)
EPSS: 71.8%
KEV: Not listed

Published

September 24, 2019

Last Modified

November 21, 2024

References (6)

cve@mitrehttps://lists.openinfosecfoundation.org/pipermail/oisf-announce/
cve@mitrehttps://suricata-ids.org/2019/09/24/suricata-4-1-5-released/
cve@mitrehttps://www.code-intelligence.com/cve-2019-16410
af854a3a-2127-422b-91ae-364da2661108https://lists.openinfosecfoundation.org/pipermail/oisf-announce/
af854a3a-2127-422b-91ae-364da2661108https://suricata-ids.org/2019/09/24/suricata-4-1-5-released/
af854a3a-2127-422b-91ae-364da2661108https://www.code-intelligence.com/cve-2019-16410

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-125Out-of-bounds Read

Data Freshness Timeline

(refreshed 13× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-05 06:08 UTCepss_batch
2026-06-05 06:08 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-04 13:10 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-31 00:14 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 14:00 UTCEG score recompute
2026-05-27 14:00 UTCGHSA enrichment
2026-05-27 13:38 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch

Frequently asked(5)

What is CVE-2019-16410?

CVE-2019-16410 is a critical vulnerability published on September 24, 2019. An issue was discovered in Suricata 4.1.4. By sending multiple fragmented IPv4 packets, the function Defrag4Reassemble in defrag.c tries to access a memory region that is not allocated, because of a lack of header_len checking.

When was CVE-2019-16410 disclosed?

CVE-2019-16410 was first published in the National Vulnerability Database on September 24, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2019-16410 actively exploited?

CVE-2019-16410 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2019-16410?

CVE-2019-16410 has a CVSS v3 base score of 9.1 (NVD).

How do I remediate CVE-2019-16410?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-16410, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2019-16410

Explore →

Is Your Infrastructure Affected by CVE-2019-16410?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2019-16410

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-16410?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)