Arne Welzel b21e6f72da HTTP: Make Content-Range parsing more robust ... This was exposed by OSS-Fuzz after the HTTP/0.9 changes in zeek/zeek#2851: We do not check the result of parsing the from and last bytes of a Content-Range header and would reference uninitialized values on the stack if these were not valid. This doesn't seem as bad as it sounds outside of yielding non-sensible values: If the result was negative, we weird/bailed. If the result was positive, we already had to treat it with suspicion anyway and the SetPlainDelivery() logic accounts for that.		2023-03-13 18:00:39 +01:00
..
files	X.509: expose the signature type inside the tbs certificate	2023-02-28 19:24:16 +00:00
frameworks	logging: Add telemetry for streams and log writers	2023-02-27 12:51:03 +01:00
misc	Add scripts.base.misc.installation btest	2022-05-23 14:16:59 -07:00
protocols	HTTP: Make Content-Range parsing more robust	2023-03-13 18:00:39 +01:00
utils	Spelling testing	2022-11-16 20:05:03 -05:00