QEMU drive_init function security bypass

qemu-driveinit-security-bypass (42268) The risk level is classified as MediumMedium Risk


QEMU could allow a local attacker to bypass security restrictions caused by an error in the drive_init function. By writing a header to a raw formatted disk image that specifies another image format, an attacker on a guest instance could exploit this vulnerability to read arbitrary files on the host.


Base Score: 2.1
  Access Vector: Local
  Access Complexity: Low
  Authentication: None
  Confidentiality Impact: Partial
  Integrity Impact: None
  Availability Impact: None
Temporal Score: 1.6
  Exploitability: Unproven
  Remediation Level: Official-Fix
  Report Confidence: Confirmed


Bypass Security


Refer to the QEMU SVN repository for patch, upgrade or suggested workaround information. See References.


Platforms Affected:

  • Canonical Ubuntu 8.04 LTS
  • Canonical Ubuntu 8.10
  • Fabrice Bellard QEMU 0.9.1
  • MandrakeSoft Mandrake Linux 2008.0 X86_64
  • MandrakeSoft Mandrake Linux 2008.0
  • MandrakeSoft Mandrake Linux 2008.1 X86_64
  • MandrakeSoft Mandrake Linux 2008.1
  • RedHat Enterprise Linux 5
  • RedHat Enterprise Linux 5 Client
  • RedHat Enterprise Linux 5.1.z EUS
  • RedHat RHEL Desktop Multi OS 5 Client
  • RedHat RHEL Virtualization 5 Server
  • RedHat RHEL Virtualization 5.1.z EUS


Apr 28, 2008

The information within this database may change without notice. Use of this information constitutes acceptance for use in an AS IS condition. There are NO warranties, implied or otherwise, with regard to this information or its use. Any use of this information is at the user's risk. In no event shall the author/distributor (IBM Internet Security Systems X-Force) be held liable for any damages whatsoever arising out of or in connection with the use or spread of this information.

For corrections or additions please email ignore thisxforceignore this@ignore thisus.ignore thisibm.comignore this

Return to the main page