Closed jkh19 closed 1 year ago
It is supposed to ignore zero-length EXIF's, but a missing length check turned into an internal error.
The fix will be shipped in a new release soon.
@randy408 - Great, thanks for merging in the fix.
Do you happen to have a general idea around a planned release schedule? I am just trying to weigh the option of investigating workarounds in the meantime.
Thanks!
I'd say less than a week for a new stable release.
Describe the issue While using the Sharp library in a downstream application, we've encountered >100 images that could not be processed due to
Input file has corrupt header: pngload: reached chunk/cache limits
errors.After reporting the issue to the Sharp library, it was discovered that the root cause is that these PNG images have zero-length chunks for the EXIF chunk, which must be at least 4 bytes to determine endianness.
It was suggested to open this upstream issue with a link to https://github.com/randy408/libspng/issues/14 to see if this use case falls under the category of conformance vs compatibility.
To Reproduce
Attempt to use the following PNG image with the library:
Receive
Input file has corrupt header: pngload: reached chunk/cache limits
.Platform (please complete the following information):
Additional analysis of PNG file