Bug#770425: wordpress: 4.0.1 security release

2014-11-26 Thread Yves-Alexis Perez
On sam., 2014-11-22 at 21:45 +0100, Yves-Alexis Perez wrote: > On Sat, 22 Nov 2014 19:13:26 +1100 Craig Small wrote: > > On Fri, Nov 21, 2014 at 08:19:03AM +0100, Salvatore Bonaccorso wrote: > > > Setting this as severity grave as it is mentioned as critical update. > > > See https://wordpress.org

Bug#770425: wordpress: 4.0.1 security release

2014-11-25 Thread Salvatore Bonaccorso
Control: retitle -1 wordpress: CVE-2014-9031 CVE-2014-9032 CVE-2014-9033 CVE-2014-9034 CVE-2014-9035 CVE-2014-9036 CVE-2014-9037 CVE-2014-9038 CVE-2014-9039 (issues fixed in 4.0.1 security release) Hi, On Fri, Nov 21, 2014 at 08:19:03AM +0100, Salvatore Bonaccorso wrote: > Source: wordpress > V

Bug#770425: wordpress: 4.0.1 security release

2014-11-22 Thread Yves-Alexis Perez
On Sat, 22 Nov 2014 19:13:26 +1100 Craig Small wrote: > On Fri, Nov 21, 2014 at 08:19:03AM +0100, Salvatore Bonaccorso wrote: > > Setting this as severity grave as it is mentioned as critical update. > > See https://wordpress.org/news/2014/11/wordpress-4-0-1/ for details. > Thanks for the heads-up

Bug#770425: wordpress: 4.0.1 security release

2014-11-22 Thread Craig Small
On Fri, Nov 21, 2014 at 08:19:03AM +0100, Salvatore Bonaccorso wrote: > Setting this as severity grave as it is mentioned as critical update. > See https://wordpress.org/news/2014/11/wordpress-4-0-1/ for details. Thanks for the heads-up, I knew it was out there but was waiting for some free time.

Bug#770425: wordpress: 4.0.1 security release

2014-11-20 Thread Salvatore Bonaccorso
Source: wordpress Version: 3.6.1+dfsg-1 Severity: grave Tags: security upstream fixed-upstream Hi Setting this as severity grave as it is mentioned as critical update. See https://wordpress.org/news/2014/11/wordpress-4-0-1/ for details. There are no CVEs assigned yet for these issues. Regards,