-
-
Notifications
You must be signed in to change notification settings - Fork 705
Fix a crash in jxlsave #3620
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
Fix a crash in jxlsave #3620
Conversation
Some versions of GraphicsMagick can report rgb colourspace for some mono BMPs. In turn, this can trigger a crash in jxlsave. See #3619
Some tests fail if you run with graphicsmagick, but I don't see an easy way to fix them, unfortunately. I suppose we'd need some way for pyvips to detect if libvips was running with graphicsmagick. |
Co-authored-by: Lovell Fuller <[email protected]>
Co-authored-by: Lovell Fuller <[email protected]>
🤦 thanks Lovell, copy-paste error :( |
I could cherry-pick this to 8.14 and make a new release if needed. However, given that we already warn users in our documentation about the security concerns when processing untrusted images via *magick, it's probably fine to leave this fix only on the master branch (assuming this crash can only occur with GraphicsMagick and v8.15.0 is released in a couple of weeks). |
Some versions of GraphicsMagick can report rgb colourspace for some mono BMPs. In turn, this can trigger a crash in jxlsave. See #3619
Some versions of GraphicsMagick can report rgb colourspace for some mono BMPs. In turn, this can trigger a crash in jxlsave. See libvips#3619 (cherry picked from commit 0297086)
Some versions of GraphicsMagick can report rgb colourspace for some mono BMPs. In turn, this can trigger a crash in jxlsave.
See #3619
@kleisauke this is against master, though since it's a crash (under some circumstances) maybe it should be cherrypicked for 8.14?