Don't panic if LZW doesn't find an LZW end code #306
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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.
|
Uff... this seems to hit a debug_assert in the underlying library: https://github.com/image-rs/weezl/blob/fa42aa42da4b611a407d1d4e0d41a72e16e3f1a7/src/decode.rs#L909-L927. What's the best way of moving this forward? Should we make the debug_assert configurable as mentioned by the doc comment? Should we run this crates fuzz-tests in release? |
|
Do you have a minimal reproduction file / lzw stream data? I thought that debug assert was being fuzzed, you can definitely open it against |
197g
approved these changes
Nov 4, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.