Re: unzip CVE-2019-13232

2019-08-03 Thread Sylvain Beucler
On 03/08/2019 14:05, Markus Koschany wrote: > Am 03.08.19 um 10:55 schrieb Sylvain Beucler: > [...] >> When an early fix is more likely to introduce regressions than protect >> users from real-world attacks, don't we mark it as 'postponed'? > We only postpone a fix if there is a minor issue and

Re: unzip CVE-2019-13232

2019-08-03 Thread Markus Koschany
Am 03.08.19 um 10:55 schrieb Sylvain Beucler: [...] > When an early fix is more likely to introduce regressions than protect > users from real-world attacks, don't we mark it as 'postponed'? We only postpone a fix if there is a minor issue and it is not worth fixing via a standalone update.

Re: unzip CVE-2019-13232

2019-08-03 Thread Markus Koschany
Hi Salvatore, Am 03.08.19 um 09:12 schrieb Salvatore Bonaccorso: [...] > The classification was done here: > > https://salsa.debian.org/security-tracker-team/security-tracker/commit/0891eec1447b20c9f45d18754f733df2081bbda3 > > I though agree with Moritz's classification on this. Should users >

[SECURITY] [DLA 1871-1] vim security update

2019-08-03 Thread Sylvain Beucler
-BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Package: vim Version: 2:7.4.488-7+deb8u4 CVE ID : CVE-2017-11109 CVE-2017-17087 CVE-2019-12735 Debian Bug : 867720 930020 Several minor issues have been fixed in vim, a highly configurable text editor. CVE-2017-11109

Re: unzip CVE-2019-13232

2019-08-03 Thread Sylvain Beucler
Hi, On Sat, Aug 03, 2019 at 09:12:32AM +0200, Salvatore Bonaccorso wrote: > On Fri, Aug 02, 2019 at 06:48:05PM +0200, Markus Koschany wrote: > > Hello Salvatore, > > > > my last email regarding unzip, CVE-2019-13232, apparently remained > > unanswered [1] but I feel it needs a clarification

Re: unzip CVE-2019-13232

2019-08-03 Thread Salvatore Bonaccorso
Hi Markus, On Fri, Aug 02, 2019 at 06:48:05PM +0200, Markus Koschany wrote: > Hello Salvatore, > > my last email regarding unzip, CVE-2019-13232, apparently remained > unanswered [1] but I feel it needs a clarification hence I am resending it. > > I don't understand why CVE-2019-13232 was