CVE-2019-10053 json
An issue was discovered in Suricata 4.1.x before 4.1.4.
published 7y ago modified 4mo ago also EUVD-2019-2116
- cvss
- 9.8
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 0
- none known
Summary
An issue was discovered in Suricata 4.1.x before 4.1.4. If the input of the function SSHParseBanner is composed only of a \n character, then the program runs into a heap-based buffer over-read. This occurs because the erroneous search for \r results in an integer underflow.
Patch / fix
- suricata-ids suricata 4.1.4
- suricata Debian 14, Debian 13 1:4.1.4-1
debian advisories DEBIAN-CVE-2019-10053
- suricata openSUSE Tumbleweed 8.0.0-1.1
opensuse advisories openSUSE-SU-2025:15394-1
Is CVE-2019-10053 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerVendor 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-10053 updated cvss 4.3
suricata: heap-based buffer over-read in function SSHParseBanner
-
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.71% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 9.8 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
References
-
suricata-ids.org
/2019/04/30/suricata-4-1-4-released/
patch, vendor-advisory
-
lists.openinfosecfoundation.org
/pipermail/oisf-announce/
third-party-advisory
Sources
- CVE List CVE-2019-10053
- NVD CVE-2019-10053
Fencer Intel 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.