[QEMU] Anúncio de segurança

[Clebson]

Uma nova falha de segurança foi descoberta a pouco tempo que afeta todos os servidores virtualizados em XEN ou KVM. Segue abaixo texto original:

 

A security flaw has been found in QEMU's Floppy Disk Controller (FDC) emulation code. It is advised you upgrade your versions of Xen/KVM as soon as possible.

This flaw only affects Xen & KVM virtualizations. No action is required for OpenVZ.

Details

An out-of-bounds memory access flaw was found in the way QEMU's virtual Floppy Disk Controller (FDC) handled FIFO buffer access while processing certain FDC commands. A privileged guest user could use this flaw to crash the guest or, potentially, execute arbitrary code on the host with the privileges of the host's QEMU process corresponding to the guest.

The flaw affects all versions of QEMU going back to 2004, when the virtual floppy controller was first introduced. Fortunately there is no known exploit that can successfully attack the flaw so far. Yet VENOM is risky enough to be considered a high-priority vulnerability. In order to mount an exploit attempt, a user on the guest machine would need sufficient permissions to access the floppy disk controller I/O ports. On Linux guests, that means the user would need to have root access or otherwise elevated privilege. But on Windows guests, practically any user would have sufficient permissions.

Upgrading a KVM Hypervisor

yum update qemu-kvm

Following the update, the guests (virtual machines) need to be powered off and started up again for the update to take effect. Please note that it is not enough to restart the guests because a restarted guest would continue running using the same (old, not updated) QEMU binary.

Upgrading a Xen Hypervisor (RHEL 6)

yum update xen

Following the update, the guests (virtual machines) need to be powered off and started up again for the update to take effect. Please note that it is not enough to restart the guests because a restarted guest would continue running using the same (old, not updated) QEMU binary.

Upgrading a Xen Hypervisor (RHEL 5)

If your hypervisor is RHEL 5 and you use the 3.4.x version of Xen please see the following document https://documentation.solusvm.com/display/DOCS/Xen+3.4.x+RPM+Releases

References
http://www.theregister.co.uk/2015/05/13/heartbleed_eat_your_heart_out_venom_vuln_poisons_countless_vms
http://venom.crowdstrike.com

 

 

Tradução livre: https://translate.google.com.br/?hl=pt-BR&tab=wT

 

Antes que alguém pergunte: This flaw only affects Xen & KVM virtualizations. No action is required for OpenVZ. (Esta falha afeta apenas as virtualizações em Xen e KVM. Nenhuma ação é necessária para OpenVZ.)

[Renato Frota]

O seu link leva pro Google Translate (sem nenhum conteúdo). Pode passar o link original, please?

 

Obrigado.

[Clebson]

O seu link leva pro Google Translate (sem nenhum conteúdo). Pode passar o link original, please?

 

Obrigado.

 

Renato, para ver o conteúdo em português você só precisa copiar o texto do tópico que esta em inglês, e colar no tradutor.

[BrunoOliveira]

Já saiu atualização, basta aplica-lá e reiniciar as VMs.

[Renato Frota]

Já saiu atualização, basta aplica-lá e reiniciar as VMs.

Reiniciar, não. Precisa desligar e ligar de novo.

[BrunoOliveira]

Pode ser... Recebi alguns Emails referente ao reinício das VMs por causa desse problema de alguns hosts da gringa... O termo utilizado por eles foi "reboot" mas pode ser desligar e ligar.

[EuMarcos]

Reiniciar, não. Precisa desligar e ligar de novo.

 

Um hard reboot apenas é necessário.

[Renato Frota]

Following the update, the guests (virtual machines) need to be powered off and started up again for the update to take effect. Please note that it is not enough to restart the guests because a restarted guest would continue running using the same (old, not updated) QEMU binary.

[Thiago Sabaia]

A Backupsy mandou esse alerta ontem, e hoje de madrugada desligaram todos servidores para aplicar as alterações.

[LucianoZ]

A Backupsy mandou esse alerta ontem, e hoje de madrugada desligaram todos servidores para aplicar as alterações.

 

Exatamente o que ocorreu comigo. rs