From: Daniel P. Berrange berra...@redhat.com
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
On 29.08.2013 12:49, Daniel P. Berrange wrote:
From: Daniel P. Berrange berra...@redhat.com
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
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 berra...@redhat.com
The parameters for the virDomainMigrate*Params RPC calls were
not bounds checks, meaning a malicious client can cause libvirtd
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 berra...@redhat.com
The parameters for the virDomainMigrate*Params RPC calls were
not bounds checks,
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 berra...@redhat.com
The parameters
