CVE-2019-10054 json
An issue was discovered in Suricata 4.1.3.
published 2019-08-28 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-2117
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 0
- none known
Summary
An issue was discovered in Suricata 4.1.3. The function process_reply_record_v3 lacks a check for the length of reply.data. It causes an invalid memory access and the program crashes within the nfs/nfs3.rs file.
Patch / fix
- suricata Debian 14, Debian 13 1:4.1.4-1
debian advisories DEBIAN-CVE-2019-10054
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2019-10054 updated cvss 8.2
suricata: invalid memory access in function process_reply_record_v3 leads to denial of service
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- redmine.openinfosecfoundation.org https://redmine.openinfosecfoundation.org/issues/2943 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:N/A:P |
Classification
References
-
redmine.openinfosecfoundation.org
/issues/2943
exploit, issue-tracking, third-party-advisory
-
suricata-ids.org
/2019/04/30/suricata-4-1-4-released/
release-notes, vendor-advisory
Sources
- CVE List CVE-2019-10054
- NVD CVE-2019-10054
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.