| CVE-2024-4418 | Date: (C)2024-05-08 (M)2024-06-21 |
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 Score and Metrics +CVSS Score and Metrics -| CVSS V3 Severity: | CVSS V2 Severity: |
| CVSS Score : 6.2 | CVSS Score : |
| Exploit Score: | Exploit Score: |
| Impact Score: | Impact Score: |
| |
| CVSS V3 Metrics: | CVSS V2 Metrics: |
| Attack Vector: | Access Vector: |
| Attack Complexity: | Access Complexity: |
| Privileges Required: | Authentication: |
| User Interaction: | Confidentiality: |
| Scope: | Integrity: |
| Confidentiality: | Availability: |
| Integrity: | |
| Availability: | |
| | |
