Race Condition Affecting libvirt-daemon-driver-storage-mpath package, versions *


Severity

Recommended
0.0
medium
0
10

Based on CentOS security rating.

Threat Intelligence

EPSS
0.05% (18th percentile)

Do your applications use this vulnerable package?

In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.

Test your applications

Snyk Learn

Learn about Race Condition vulnerabilities in an interactive lesson.

Start learning
  • Snyk IDSNYK-CENTOS7-LIBVIRTDAEMONDRIVERSTORAGEMPATH-6800318
  • published2 May 2024
  • disclosed2 May 2024

Introduced: 2 May 2024

CVE-2024-4418  (opens in a new tab)
CWE-362  (opens in a new tab)
CWE-416  (opens in a new tab)

How to fix?

There is no fixed version for Centos:7 libvirt-daemon-driver-storage-mpath.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libvirt-daemon-driver-storage-mpath package and not the libvirt-daemon-driver-storage-mpath package as distributed by Centos. See How to fix? for Centos:7 relevant fixed versions and status.

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 Scores

version 3.1