Critical NULL Pointer Dereference in libvirt Leading to Daemon Crash
Summary
DEBIAN-CVE-2024-8235: A flaw was found in libvirt. Affects libvirt versions < 10.7.0-1. Fixed in 10.7.0-1. How to fix ↓
Check if this vulnerability affects your application
Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.
No signup required · Results in about 60 seconds
Background
libvirt is an open-source API, daemon, and management tool for managing platform virtualization. It provides a consistent way to manage virtual machines, storage, and networking across different hypervisors. The libvirt package is widely used in cloud computing and virtualization environments, making it essential for system administrators and developers. However, a recent vulnerability has been identified that could lead to a crash of the virtinterfaced daemon, impacting the stability of virtualized environments.
Vulnerability Detail
A flaw was found in libvirt due to a refactor of the code responsible for fetching the list of interfaces across multiple APIs. This introduced a corner case on platforms where allocating 0 bytes of memory results in a NULL pointer. When this NULL pointer is dereferenced, it leads to a crash of the virtinterfaced daemon. Clients connecting to the read-only socket could experience service disruption as a result of this vulnerability.
How To Fix
Minimum fixed version
10.7.0-1
This is the first release that contains the fix.
sudo apt-get install --only-upgrade libvirtTip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →
Workaround
As a temporary workaround, you can avoid connecting clients to the read-only socket until the package is updated. This will prevent the potential crash of the virtinterfaced daemon while a fix is being implemented.
Conclusion
The identified vulnerability in libvirt poses a significant risk by potentially crashing the virtinterfaced daemon due to a NULL pointer dereference. It is crucial for users to update to the patched version 10.7.0-1 to mitigate this risk. Until then, implementing the suggested workaround can help maintain service stability.
See every vulnerability recorded for libvirt →
FAQ
The vulnerability can lead to a NULL pointer dereference, causing the virtinterfaced daemon to crash, which may disrupt services for clients connecting to it.
You can use the Vulert playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
If immediate updates are not possible, consider implementing the workaround by avoiding client connections to the read-only socket until the update can be applied.
Yes, the vulnerability affects libvirt versions prior to 10.7.0-1. Updating to this version or later will resolve the issue.
More information about libvirt can be found on its official website and documentation, which provide insights into its features and usage.
References
Related vulnerabilities
Recent vulnerabilities recorded for libvirt.
