-
Notifications
You must be signed in to change notification settings - Fork 76
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash with bitmap images with unsupported bis per pixel #144
Comments
Output of
|
Nevermind I apologize, this appears to be fixed in the latest release, I forgot to check |
Thanks for the report, I'll have a look. It looks like it happens somewhere in the sws scaler, so depends on that library version. It is a controlled crash, i.e. it actually calls |
Reopening for now until fully investigated. |
I was playing around with bitmap files and creating them by hand, usually timg manages to deal with uncommon / malformed formats very well, by either displaying the image anyways or silently exiting without output, but I encountered a variation where it crashes with
Magick: abort due to signal 6 (SIGABORT) "Abort"...
(Using ImageMagicks's 'display' yields a helpful error message:
unsupported bits per pixel
)This happens when asking it to display a bitmap image using BITMAPCOREHEADER that specifies an unsupported bits per pixel, i.e. 3:
minimal_error.zip contains a minimal bitmap file to reproduce the issue,
or alternatively convert the following hexdump into a binary:
This obviously isn't a huge issue, but it is possible for it to have security implications if it crashes badly instead of gracefully handling it so I thought it was worth bringing up
The text was updated successfully, but these errors were encountered: