Your submission was sent successfully! Close

Thank you for contacting us. A member of our team will be in touch shortly. Close

You have successfully unsubscribed! Close

Thank you for signing up for our newsletter!
In these regular emails you will find the latest updates about Ubuntu and upcoming events where you can meet our team.Close

CVE-2010-2239

Publication date 19 August 2010

Last updated 24 July 2024

Ubuntu priority

Medium

Why this priority?

Red Hat libvirt, possibly 0.6.0 through 0.8.2, creates new images without setting the user-defined backing-store format, which allows guest OS users to read arbitrary files on the host OS via unspecified vectors.

Read the notes from the security team

Status

Package Ubuntu Release Status
libvirt 10.10 maverick
Fixed 0.8.3-1ubuntu8
10.04 LTS lucid
Fixed 0.7.5-5ubuntu27.5
9.10 karmic
Fixed 0.7.0-1ubuntu13.2
9.04 jaunty Ignored end of life
8.04 LTS hardy
Not affected
6.06 LTS dapper Not in release

Notes

jdstrand

AppArmor in Ubuntu 9.10 and 10.04 should protect the host OS, but an attacker in a virtual machine may be able to access files of another machine. Ubuntu 9.10's qemu-img and kvm-img both support '-F backingType', so hard code libvirt to use this Ubuntu 9.04's qemu-img and kvm-img do not support specifiying a backing store disk format, so we must autoprobe backing stores at this time. Qemu didn't gain this option until 0.11, and 9.04 has 0.10 and kvm 84. The changes to qemu/kvm are too invasive and regression-prone and therefore an update will not be provided for this CVE for Ubuntu 9.04.

References

Related Ubuntu Security Notices (USN)

    • USN-1008-1
    • libvirt vulnerabilities
    • 21 October 2010

Other references