CVE-2019-10051

HIGHNVD 7.57.5—

7.5

An issue was discovered in Suricata 4.1.3. If the function filetracker_newchunk encounters an unsafe "Some(sfcm) => { ft.new_chunk }" item, then the program enters an smb/files.rs error condition and crashes.

CVSS v3: 7.5
EG Score: 7.5(medium)
EPSS: 69.7%
KEV: Not listed

Published

August 28, 2019

Last Modified

November 21, 2024

References (6)

cve@mitrehttps://github.com/OISF/suricata/pull/3734
cve@mitrehttps://redmine.openinfosecfoundation.org/issues/2896
cve@mitrehttps://suricata-ids.org/2019/04/30/suricata-4-1-4-released/
af854a3a-2127-422b-91ae-364da2661108https://github.com/OISF/suricata/pull/3734
af854a3a-2127-422b-91ae-364da2661108https://redmine.openinfosecfoundation.org/issues/2896
af854a3a-2127-422b-91ae-364da2661108https://suricata-ids.org/2019/04/30/suricata-4-1-4-released/

Weakness Classification(1)

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

CWE-754

Data Freshness Timeline

(refreshed 9× in last 7d / 17× 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-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 15:07 UTCEG score recompute
2026-05-27 15:07 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
2026-05-26 07:17 UTCepss_batch
2026-05-24 23:43 UTCOSV refresh

Frequently asked(5)

What is CVE-2019-10051?

CVE-2019-10051 is a high vulnerability published on August 28, 2019. An issue was discovered in Suricata 4.1.3. If the function filetrackernewchunk encounters an unsafe "Some(sfcm) => { ft.newchunk }" item, then the program enters an smb/files.rs error condition and crashes.

When was CVE-2019-10051 disclosed?

CVE-2019-10051 was first published in the National Vulnerability Database on August 28, 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-10051 actively exploited?

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

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

CVE-2019-10051 has a CVSS v3 base score of 7.5 (NVD).

How do I remediate CVE-2019-10051?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2019-10051, 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-10051

Explore →

Is Your Infrastructure Affected by CVE-2019-10051?

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

Start Free Scan →Browse All CVEs

CVE-2019-10051

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(1)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2019-10051?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)