CVE-2019-17420 json
In OISF LibHTP before 0.5.31, as used in Suricata 4.1.4 and other products, an HTTP protocol parsing error causes the http_header signature…
published 7y ago modified 4mo ago also EUVD-2019-7816
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 71%
- public exploits
- 0
- none known
Summary
In OISF LibHTP before 0.5.31, as used in Suricata 4.1.4 and other products, an HTTP protocol parsing error causes the http_header signature to not alert on a response with a single \r\n ending.
Patch / fix
- oisf libhtp 0.5.31
- libhtp Debian 13, Debian 12 1:0.5.31-1
debian advisories DEBIAN-CVE-2019-17420
- github.com/OISF/libhtp/compare/0.5.30...0.5.31 patch
- github.com/OISF/libhtp#213 pull request
Is CVE-2019-17420 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 FencerExploit prediction
1.36% chance of exploitation in the next 30 days, higher than 71% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-459 Incomplete Cleanup
References
-
github.com
/OISF/libhtp/pull/213
patch, third-party-advisory
-
github.com
/OISF/libhtp/compare/0.5.30...0.5.31
patch
-
redmine.openinfosecfoundation.org
/issues/2969
issue-tracking, vendor-advisory
Sources
- CVE List CVE-2019-17420
- NVD CVE-2019-17420
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.