Re: [libvirt] [PATCH 01/12] Add bounds checking on virDomainMigrate*Params RPC calls (CVE-2013-4292)

2013-08-29 Thread Daniel P. Berrange
On Thu, Aug 29, 2013 at 02:58:44PM +0200, Michal Privoznik wrote: > On 29.08.2013 14:55, Daniel P. Berrange wrote: > > On Thu, Aug 29, 2013 at 02:34:15PM +0200, Michal Privoznik wrote: > >> On 29.08.2013 12:49, Daniel P. Berrange wrote: > >>> From: "Daniel P. Berrange" > >>> > >>> The parameters f

Re: [libvirt] [PATCH 01/12] Add bounds checking on virDomainMigrate*Params RPC calls (CVE-2013-4292)

2013-08-29 Thread Michal Privoznik
On 29.08.2013 14:55, Daniel P. Berrange wrote: > On Thu, Aug 29, 2013 at 02:34:15PM +0200, Michal Privoznik wrote: >> On 29.08.2013 12:49, Daniel P. Berrange wrote: >>> From: "Daniel P. Berrange" >>> >>> The parameters for the virDomainMigrate*Params RPC calls were >>> not bounds checks, meaning a

Re: [libvirt] [PATCH 01/12] Add bounds checking on virDomainMigrate*Params RPC calls (CVE-2013-4292)

2013-08-29 Thread Daniel P. Berrange
On Thu, Aug 29, 2013 at 02:34:15PM +0200, Michal Privoznik wrote: > On 29.08.2013 12:49, Daniel P. Berrange wrote: > > From: "Daniel P. Berrange" > > > > The parameters for the virDomainMigrate*Params RPC calls were > > not bounds checks, meaning a malicious client can cause libvirtd > > to consu

Re: [libvirt] [PATCH 01/12] Add bounds checking on virDomainMigrate*Params RPC calls (CVE-2013-4292)

2013-08-29 Thread Michal Privoznik
On 29.08.2013 12:49, Daniel P. Berrange wrote: > From: "Daniel P. Berrange" > > The parameters for the virDomainMigrate*Params RPC calls were > not bounds checks, meaning a malicious client can cause libvirtd > to consume arbitrary memory > > This issue was introduced in the 1.1.0 release of lib

[libvirt] [PATCH 01/12] Add bounds checking on virDomainMigrate*Params RPC calls (CVE-2013-4292)

2013-08-29 Thread Daniel P. Berrange
From: "Daniel P. Berrange" The parameters for the virDomainMigrate*Params RPC calls were not bounds checks, meaning a malicious client can cause libvirtd to consume arbitrary memory This issue was introduced in the 1.1.0 release of libvirt Signed-off-by: Daniel P. Berrange --- daemon/remote.c