Hi Nikita, it's always nice when you can test directly if a known bad input has been handled correctly, but not all security fixes come with sample inputs to see the issue. So when you can find them, that's always welcome, but not necessary.
But it is necessary to make sure that programs that use openjpeg can still use it correctly after the update -- e.g., a selection of tools that use openjpeg should still be able to read their inputs or create their outputs after the updated packages have been installed. If you yourself don't use openjpeg based tools perhaps someone else who does could help with the testing. Thanks -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1630702 Title: CVE-2016-8332 allows an out-of-bound heap write to occur resulting in heap corruption and arbitrary code execution To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/openjpeg/+bug/1630702/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
