Homepage

Incorrect Permission Assignment for Critical Resource Affecting libvirt-lock-sanlock package, versions <0:4.5.0-23.2.0.1.module+el8.0.0+5225+ce2eb65e

Severity

 Recommended
0.0
high
0
10

Based on Oracle Linux security rating.

Threat Intelligence

EPSS
0.37% (73rd 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 IDSNYK-ORACLE8-LIBVIRTLOCKSANLOCK-2532900
  • published10 Apr 2022
  • disclosed22 May 2019
Report a new vulnerability Found a mistake?

Introduced: 22 May 2019

CVE-2019-10132  (opens in a new tab)
CWE-732  (opens in a new tab)

How to fix?

Upgrade Oracle:8 libvirt-lock-sanlock to version 0:4.5.0-23.2.0.1.module+el8.0.0+5225+ce2eb65e or higher.
This issue was patched in ELSA-2019-1268.

NVD Description

Note: Versions mentioned in the description apply only to the upstream libvirt-lock-sanlock package and not the libvirt-lock-sanlock package as distributed by Oracle. See How to fix? for Oracle:8 relevant fixed versions and status.

A vulnerability was found in libvirt >= 4.1.0 in the virtlockd-admin.socket and virtlogd-admin.socket systemd units. A missing SocketMode configuration parameter allows any user on the host to connect using virtlockd-admin-sock or virtlogd-admin-sock and perform administrative tasks against the virtlockd and virtlogd daemons.

References