-
Notifications
You must be signed in to change notification settings - Fork 6.8k
[WIP][Dependency Update] Upgrade the libtiff to 4.0.10 #14623
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Thank you for the fix!
Thanks for your contributions @stu1130. The CI seems to be failing. Can you look into this ? |
Sorry that I merged the PR by mistake. Do we need to revert the PR, since the CI has been passed? |
@wkcn the previous CI failures don't seem to be related to this. There is CI test for building the static library which dependes on this (I'm not sure if the CI has tests specifically for this dependency though). In any case, it doesn't seem like a revert is urgently necessary right now. |
@szha Thank you! I will pay more attention next time. |
The stattic build should trigger and verify the script to see if it is working. |
@wkcn Static build CPU 14.04 Python and Static build CPU 14.04 Scala in ubuntu cpu have tested against the script. I just want to make sure it also works in ubuntu 16.04. Since we're still using ubuntu 14.04 to build the package so no worry. Thanks for your hard work |
* upgrade the libtiff to 4.0.10 * retrigger CI * retrigger CI * retrigger CI * Retrigger CI
I triggered the vulnerability from the C library Libtiff 4.0.9, when I use an older version of incubator-mxnet, causing out-of-bounds write in the buffer. A call chain that accesses to the vulnerable function JBIGDecode() is as follows:
I have upgraded to incubator-mxnet's newest version to avoid the issues. Give the info in this report for sharing. It seems that our python projects should keep an eye on the CVEs of C libraries. |
By the way, incubator-mxnet depends on libmxnet.so, I figured out the shared library comes from Libtiff 4.0.9 based on incubator-mxnet's development docs. |
Description
please don't merge until I add publish test on CI for cuda part
Upgrade the libtiff package to 4.0.10 due to lots of issues at 4.0.9.
Please find more on CVE
Checklist
Essentials
Changes
Comments