Bug#834843: ruby-doorkeeper: CVE-2016-6582

2016-08-27 Thread Salvatore Bonaccorso
Hi! On Sat, Aug 27, 2016 at 02:58:13PM +0530, Pirate Praveen wrote: > On Thu, 25 Aug 2016 21:44:23 +0200 Salvatore Bonaccorso > wrote: > > Control: fixed -1 4.2.0-1 > > Hi > > > > This seems to have been addressed in 4.2.0 upstream (which was > > uploaded to experimental),

Bug#834843: ruby-doorkeeper: CVE-2016-6582

2016-08-27 Thread Pirate Praveen
On Thu, 25 Aug 2016 21:44:23 +0200 Salvatore Bonaccorso wrote: > Control: fixed -1 4.2.0-1 > Hi > > This seems to have been addressed in 4.2.0 upstream (which was > uploaded to experimental), but the debian/changelog does not mention > the bug closer nor the CVE id; any reason

Bug#834843: ruby-doorkeeper: CVE-2016-6582

2016-08-25 Thread Salvatore Bonaccorso
Control: fixed -1 4.2.0-1 Hi This seems to have been addressed in 4.2.0 upstream (which was uploaded to experimental), but the debian/changelog does not mention the bug closer nor the CVE id; any reason for that or just an oversight? Regards, Salvatore

Bug#834843: ruby-doorkeeper: CVE-2016-6582

2016-08-19 Thread Salvatore Bonaccorso
Source: ruby-doorkeeper Version: 3.1.0-1 Severity: grave Tags: security upstream patch Forwarded: https://github.com/doorkeeper-gem/doorkeeper/issues/875 Hi, the following vulnerability was published for ruby-doorkeeper. CVE-2016-6582[0]: Doorkeeper does not revoke tokens and wrong auth/auth