An attacker can exploit this by providing a maliciously crafted, standards-compliant 8-bit grayscale lossless JPEG. The buffer overflow occurs because there is no geometry validation comparing the libjpeg output dimensions against the allocated state->buffer. Depending on the image dimensions and requested scaling factors, this can result in writing attacker-controlled pixel data past the end of the heap-allocated buffer. While the library ultimately throws an OSError due to geometry mismatches, the memory corruption occurs during the decompression process.

Attack Chain

1. Attacker crafts a standards-compliant 8-bit grayscale lossless (SOF3) JPEG image file.
2. Attacker hosts or delivers the file to a target system utilizing a vulnerable version of Pillow.
3. The victim application calls Image.open() on the malicious file, which is parsed successfully by Pillow's SOF parser.
4. The application calls Image.thumbnail() or JpegImageFile.draft() on the image object, triggering a scaling request (e.g., scale factor s >= 2).
5. Pillow computes expected scaled dimensions and allocates a state->buffer using calloc based on the reduced size.
6. The ImagingJpegDecode function calls jpeg_start_decompress and proceeds to jpeg_read_scanlines without validating the actual JPEG output dimensions.
7. libjpeg-turbo writes the full-width pixel scanlines into the undersized buffer, causing an out-of-bounds heap write of (W - ceil(W/s)) x components bytes.
8. The overflow corrupts heap memory with attacker-controlled pixel values.

Impact

Successful exploitation allows for memory corruption on systems using Pillow to process user-supplied images. This can lead to application crashes or potentially arbitrary code execution depending on the heap layout and the ability to influence memory state through crafted pixel data. This vulnerability affects any system or service that automatically generates thumbnails or processes image uploads using Pillow with standard library defaults.

Recommendation

1. Identify and inventory all applications within the environment that utilize the Pillow library for image processing.
2. Implement strict input validation or sanitization for JPEG files to detect or reject lossless (SOF3) images if the functionality is not explicitly required.
3. Monitor internal application logs for OSError exceptions originating from PIL.JpegImagePlugin or libImaging during image processing, as these may indicate attempted exploitation.
4. Apply patches provided by the Pillow project as soon as they become available for the affected versions.