Don't panic if LZW doesn't find an LZW end code

Browse Source

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.

...

This commit is contained in:

Bastian Kersting committed 2025-10-31 06:17:35 +00:00

1 parent 2ccbe132e0

commit edd260fe7e

2 files changed

-3

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download Patch File Download Diff File Expand all files Collapse all files

No files matched your search

tests/fuzz_images/oor_panic/sample-get-lzw-stuck.tiff

BIN

Binary file not shown.