zeek/testing/btest/Traces/smtp
Arne Welzel ae2a5c83a4 SMTP: No state update for bad BDAT commands
OSS-Fuzz found that providing an invalid BDAT line would tickle an
assert in UpdateState(). The BDAT state was never initialized, but
within UpdateState() that was expected.

This also removes the AnalyzerViolation() call for bad BDAT commands
and instead raises a weird. The SMTP analyzer is very lax and not triggering
the violation allows to parse the server's response to such an invalid
command.

PCAP files produced by a custom Python SMTP client against Postfix.
2024-01-15 18:25:41 +01:00
..
rfc3030-bdat-0-last.pcap SMTP: Add BDAT support 2024-01-12 10:18:07 +01:00
rfc3030-bdat-example1.pcap SMTP: Add BDAT support 2024-01-12 10:18:07 +01:00
rfc3030-bdat-multipart-chunked.pcap SMTP: Add BDAT support 2024-01-12 10:18:07 +01:00
rfc3030-bdat-multipart.pcap SMTP: Add BDAT support 2024-01-12 10:18:07 +01:00
smtp-bdat-cmd-invalid.pcap SMTP: No state update for bad BDAT commands 2024-01-15 18:25:41 +01:00
smtp-bdat-pipeline-8bitmime.pcap btest/smtp: Test with smtp-bdat-pipeline-8bitmime.pcap 2024-01-12 10:18:14 +01:00