Bug#932673: docker.io: CVE-2019-13509

2019-08-15 Thread Arnaud Rebillout
On 8/13/19 12:31 PM, Salvatore Bonaccorso wrote: The severity does indeed not need to imply that or a no-dsa necessarily. In this concrete case we have already marked the issue as no-dsa though: https://security-tracker.debian.org/tracker/CVE-2019-13509 Thanks for the link! I thought the no-d

Bug#932673: docker.io: CVE-2019-13509

2019-08-13 Thread Salvatore Bonaccorso
Hi Arnaud, On Tue, Aug 13, 2019 at 11:28:08AM +0200, Arnaud Rebillout wrote: > This is fixed in unstable. > > Question from a non-experienced DM: severity is "normal", should I > understand that this fix shouldn't be included in stable? Or should I > expect an explicit "no-dsa" tag? The severity

Bug#932673: docker.io: CVE-2019-13509

2019-08-13 Thread Arnaud Rebillout
This is fixed in unstable. Question from a non-experienced DM: severity is "normal", should I understand that this fix shouldn't be included in stable? Or should I expect an explicit "no-dsa" tag? Thanks,   Arnaud

Bug#932673: docker.io: CVE-2019-13509

2019-07-21 Thread Salvatore Bonaccorso
Source: docker.io Version: 18.09.1+dfsg1-7.1 Severity: normal Tags: security upstream Control: found -1 18.09.5+dfsg1-1 Hi, The following vulnerability was published for docker.io. If I do understand the isuse correctly, then I do not think there is any urgend action to be taken for buster, it mi