You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oss-fuzz has found a test case where (when accessed via GraphicsMagick) libheif allows libjpeg to exit due to its default error handler if libheif is compiled with JPEG support (likely a rare configuration). Libjpeg clients normally use setjmp/longjmp for error handling. The error message which comes out (produced by libjpeg) is "Empty input file".
Oss-fuzz has found a test case where (when accessed via GraphicsMagick) libheif allows libjpeg to exit due to its default error handler if libheif is compiled with JPEG support (likely a rare configuration). Libjpeg clients normally use setjmp/longjmp for error handling. The error message which comes out (produced by libjpeg) is "Empty input file".
If I use libheif's utilities I see results like:
and
The POC file is attached with a jpg extension to satisfy github:
Please advise if special error handling methodologies are required to deal with this.
The text was updated successfully, but these errors were encountered: