We use these services and cookies to improve your user experience. You may opt out if you wish, however, this may limit some features on this site.
Please see our statement on Data Privacy.
Assigner | redhat |
Reserved | 2024-05-02 |
Published | 2024-05-08 |
Updated | 2024-09-13 |
A race condition leading to a stack use-after-free flaw was found in libvirt. Due to a bad assumption in the virNetClientIOEventLoop() method, the `data` pointer to a stack-allocated virNetClientIOEventData structure ended up being used in the virNetClientIOEventFD callback while the data pointer's stack frame was concurrently being "freed" when returning from virNetClientIOEventLoop(). The 'virtproxyd' daemon can be used to trigger requests. If libvirt is configured with fine-grained access control, this issue, in theory, allows a user to escape their otherwise limited access. This flaw allows a local, unprivileged user to access virtproxyd without authenticating. Remote users would need to authenticate before they could access it.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
2024-05-02: | Reported to Red Hat. |
2024-05-02: | Made public. |
Red Hat would like to thank Martin Širokov for reporting this issue.
https://access.redhat.com/errata/RHSA-2024:4351 (RHSA-2024:4351)
https://access.redhat.com/errata/RHSA-2024:4432 (RHSA-2024:4432)
https://access.redhat.com/errata/RHSA-2024:4757 (RHSA-2024:4757)
https://access.redhat.com/security/cve/CVE-2024-4418
https://bugzilla.redhat.com/show_bug.cgi?id=2278616 (RHBZ#2278616)