Bastian Kersting edd260fe7e Don't panic if LZW doesn't find an LZW end code ...

Currently, when getting the LZWStatus::NoProgress from the underlying
weezl library, tiff checks that no input bytes were read and no
output bytes were written. Although this is according to what the
weezl library mentions in their doc-comment, it's not what the real
result always looks like.

Our fuzzer found input that triggered exactly this case, where the LZW
reader is able to write some output byte before hitting the NoProgress
status.

This change removes the assert, as the resulting action is anyways to return
an error that can be handled by the caller.

2025-10-31 06:17:35 +00:00

6.9 KiB

Raw History

View Raw