First published: Thu Jun 24 2010(Updated: )
It was found that libvirt did not explicitly set the user defined backing store format when creating new image. This results in images being created with an potentialy insecure configuration, preventing applications from opening backing stores without resorting to probing. A priviledged guest user could use this flaw to access arbitrary files on the host.
Credit: secalert@redhat.com
Affected Software | Affected Version | How to fix |
---|---|---|
libvirt | =0.6.0 | |
libvirt | =0.6.1 | |
libvirt | =0.6.2 | |
libvirt | =0.6.3 | |
libvirt | =0.6.4 | |
libvirt | =0.6.5 | |
libvirt | =0.7.0 | |
libvirt | =0.7.1 | |
libvirt | =0.7.2 | |
libvirt | =0.7.3 | |
libvirt | =0.7.4 | |
libvirt | =0.7.5 | |
libvirt | =0.7.6 | |
libvirt | =0.7.7 | |
libvirt | =0.8.0 | |
libvirt | =0.8.1 | |
libvirt | =0.8.2 |
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
CVE-2010-2239 has a moderate severity rating due to the potential for insecure image configurations in libvirt.
To fix CVE-2010-2239, you should upgrade your libvirt installation to a version above 0.8.2 that explicitly sets the backing store format.
CVE-2010-2239 affects libvirt versions from 0.6.0 to 0.8.2.
Yes, a privileged guest user may exploit CVE-2010-2239 to create images in an insecure manner.
CVE-2010-2239 can lead to security liabilities where applications cannot reliably open backing stores due to the insecure configuration.