Libvirt: stack use-after-free in virnetclientioeventloop()
Résumé
Libvirt: stack use-after-free in virnetclientioeventloop()
Description d'origine
La description telle que publiée par la source (souvent en anglais).
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.
État des correctifs par distribution
Paquets corrigés publiés par chaque distribution pour cette CVE
- Debian DEBIAN-CVE-2024-4418 libvirt Corrigé dans: 10.3.0-1
Références
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory github.com
- advisory nvd.nist.gov
- advisory security.netapp.com
- package gitlab.com
- report bugzilla.redhat.com
- web access.redhat.com
- web lists.fedoraproject.org
- web lists.fedoraproject.org