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.
History

No history.

cve-icon MITRE

Status: PUBLISHED

Assigner: redhat

Published: 2024-05-08T03:03:05.135Z

Updated: 2024-09-13T21:21:46.385Z

Reserved: 2024-05-02T10:52:32.129Z

Link: CVE-2024-4418

cve-icon Vulnrichment

Updated: 2024-08-01T20:40:47.120Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2024-05-08T03:15:07.203

Modified: 2024-09-13T22:15:02.123

Link: CVE-2024-4418

cve-icon Redhat

Severity : Moderate

Publid Date: 2024-05-02T00:00:00Z

Links: CVE-2024-4418 - Bugzilla