Repository navigation
Conversation
…en decoding jpegs A TEM marker (FF 01) between header segments was read as a marker with a length field, so the next segment header was consumed as its length and decoding failed. TEM stands alone like RSTn, so skip it the same way. Some producers write extraneous bytes before restart markers. Those that form a TEM or reserved marker (FF 01 to FF BF) were taken as the end of the scan, which corrupted the rest of the image or made the marker parser fail. Skip them while looking for the marker that ends a restart interval and resync at the next marker, as libjpeg does.
3 of 4 tasks
4 tasks done
This branch has not been deployed
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Prerequisites
Description
JPEG header parsing treated the standalone TEM marker as a segment with a length field. It now skips TEM without consuming bytes from the next segment. This applies to both identification and decoding under every integrity policy. ITU T.81 Table B.1 defines TEM as a standalone marker.
At restart boundaries, TEM and reserved marker codes could end a scan early. The shared
JpegBitReadernow scans past those codes only whenSegmentIntegrityHandling.IgnoreImageDatapermits recovery.StrictandIgnoreAncillaryreject them. Real segment markers remain available to the segment parser. Both Huffman and arithmetic scans use this path. Arithmetic restart handling also classifies the detected marker before resetting the reader, so it does not lose the next segment marker.The cases are in the existing
JpegDecoderTests.cs, beside the extraneous-marker regression. The added standalone test file is removed. Tests load stored inputs; they do not encode or modify images at runtime. Local libjpeg-turbo 3.1.91 generated the clean inputs. Its decoder produces identical pixels for each clean/corrupted pair, with warnings for the corrupted inputs. ImageSharp checks exact pixel equality for recovery and checks rejection under the other policies. Header tests also check that an invalid required DQT length remains fatal in every mode.The arithmetic inputs declare their conditioning tables explicitly. A separate existing defect rejects progressive arithmetic input when it relies on the standard AC conditioning defaults. This PR does not change that behavior.
Validation: Release JPEG and TIFF tests pass on .NET 10 and .NET 11: 1,571 passed, one existing debug-only skip, zero failed on each target. No tolerances, reference images, or
BufferedReadStreamcode changed.V4 backport: #3258.
Fixes #3237