Date: Fri, 5 Aug 2016 17:19:25 -0700 From: Kevin Oberman <rkoberman@gmail.com> To: koobs@freebsd.org Cc: Mailinglists FreeBSD <freebsd-questions@freebsd.org>, FreeBSD Ports ML <freebsd-ports@freebsd.org>, alexmiroslav@gmail.com, FreeBSD Ports Security Team <ports-secteam@freebsd.org>, Matthew Seaman <matthew@freebsd.org> Subject: Re: tiff vulnerability in ports? Message-ID: <CAN6yY1s5SL_dZviE=hMUzT=znieHC96dHB%2BsE6pHaJoYZM2TrQ@mail.gmail.com> In-Reply-To: <b05d61de-03e7-0599-17c9-0d055ac8ab61@FreeBSD.org> References: <CACcSE1z4m_o9z2Ttw-Sb7bNhVmnwDrVX8BQFfa2a_dBbW_hwyw@mail.gmail.com> <CAJN5%2BGtsJ=n2m8Xz5eZj92yo5vFZST0dO1ZnLCpmf4x0H95w-Q@mail.gmail.com> <33ac70de-78b6-dc54-e81f-3153d0d721e4@FreeBSD.org> <b05d61de-03e7-0599-17c9-0d055ac8ab61@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, Aug 5, 2016 at 8:43 AM, Kubilay Kocak <koobs@freebsd.org> wrote: > On 5/08/2016 11:35 PM, Matthew Seaman wrote: > > On 2016/08/05 13:55, alphachi wrote: > >> Please see this link to get more information: > >> > >> https://svnweb.freebsd.org/ports?view=revision&revision=418585 > >> > >> 2016-08-05 0:23 GMT+08:00 Aleksandr Miroslav <alexmiroslav@gmail.com>: > >> > >>> This is perhaps a question for the tiff devs more than anything, but I > >>> noticed that pkg audit has been complaining about libtiff > (graphics/tiff) > >>> for some time now. > >>> > >>> FreeBSD's VUXML database says anything before 4.0.7 is affected, but > >>> apparently that version hasn't been released yet (according to > >>> http://www.remotesensing.org/libtiff/, the latest stable release is > still > >>> 4.0.6). > >>> > >>> Anyone know what's going on? Is there a release upcoming to fix this? > > > > Yeah -- this vulnerability: > > > > https://vuxml.freebsd.org/freebsd/c17fe91d-4aa6-11e6- > a7bd-14dae9d210b8.html > > > > has been in VuXML since 2016-07-15 but there's no indication of a 4.0.7 > > release from upstream yet. > > > > Given their approach to fixing the buffer overflow was to delete the > > offending gif2tiff application from the package, perhaps we could simply > > do the same until 4.0.7 comes out. > > > > Cheers, > > > > Matthew > > > > > > Hi Aleksandr :) > > Also: > > https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=211405 > > Please add a comment to that bug to request resolution of the issue. > > Alternatively you (and anyone else) can just delete gif2tiff > > Unfortunately you are yet one more example of a user that's been left in > the lurch without information or recourse wondering (rightfully) how > they can resolve or mitigate this vulnerability. Our apologies. > > This one is really annoying in that it is so easily fixed. Just modify the port to not build or even not install gif2tiff. It's not going to be fixed upstream. At least the last message in the bugzilla indicates that the program will simply be removed from 4.0.7 whenever it comes out. FreeBSD should get out front and just delete it now. A fix is trivial, but touches 20 files and, of course, the plist. Guess I should add it to the ticket. -- Kevin Oberman, Part time kid herder and retired Network Engineer E-mail: rkoberman@gmail.com PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAN6yY1s5SL_dZviE=hMUzT=znieHC96dHB%2BsE6pHaJoYZM2TrQ>