CVE-2019-17420
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.
Does this matter?
Lower severity and a low EPSS score (1.35%). Track it; it rarely justifies an emergency change on its own.
Description
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.
- CVSS 3.1
- 5.3 MEDIUMCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
- EPSS
- 1.35% probability · 71th percentile
- Public exploits
- None in Exploit-DB
- CISA KEV
- Not listed
- Weakness
- CWE-459
- Affected
- oisf/libhtp · suricata-ids/suricata
- Source
- cve@mitre.org
EPSS 1.4% since 26 October 2026; no change recorded yet. Points are recorded when the score first appears and whenever it moves by a percentage point or more.
References
- https://github.com/OISF/libhtp/compare/0.5.30...0.5.31Patch
- https://github.com/OISF/libhtp/pull/213Patch, Third Party Advisory
- https://redmine.openinfosecfoundation.org/issues/2969Issue Tracking, Vendor Advisory
- https://github.com/OISF/libhtp/compare/0.5.30...0.5.31Patch
- https://github.com/OISF/libhtp/pull/213Patch, Third Party Advisory
- https://redmine.openinfosecfoundation.org/issues/2969Issue Tracking, Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA, exploits from Exploit-DB. Refreshed daily. Download this record as JSON.