# CVE-2019-3831: Privilege escalation in vdsm > A local attacker with vdsm system user access can execute arbitrary commands as root via the systemd_run function, leading to full system compromise. - **Severity:** Medium 6.4 (`CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Local or same network only - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 25 Mar 2019 - **Updated:** 4 Aug 2024 - **Also known as:** GHSA-mgfj-qcpq-xx99, RHBA-2019:1965, RHSA-2019:0458 ## What is CVE-2019-3831? CVE-2019-3831 is a medium-severity vulnerability in [UNKNOWN] vdsm, published on 25 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim. ### Official description A vulnerability was discovered in vdsm, version 4.19 through 4.30.3 and 4.30.5 through 4.30.8. The systemd_run function exposed to the vdsm system user could be abused to execute arbitrary commands as root. Weakness: CWE-863 (Incorrect Authorization) ## Which versions are affected by CVE-2019-3831? It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `vdsm` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-api` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-client` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-common` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-gluster` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-checkips` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-cpuflags` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-ethtool-options` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-extra-ipv4-addrs` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-fcoe` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-localdisk` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-macspoof` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-nestedvt` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-openstacknet` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-vhostmd` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-hook-vmfex-dev` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-http` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-jsonrpc` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-network` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-python` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `vdsm-yajsonrpc` | Red Hat:enterprise_linux:7::hypervisor | All versions | 0:4.20.47-1.el7ev | | `ioprocess` | Red Hat:storage:3.4:server:el7 | All versions | 0:1.1.2-1.el7ev | | `ioprocess-debuginfo` | Red Hat:storage:3.4:server:el7 | All versions | 0:1.1.2-1.el7ev | | `python2-ioprocess` | Red Hat:storage:3.4:server:el7 | All versions | 0:1.1.2-1.el7ev | | `safelease` | Red Hat:storage:3.4:server:el7 | All versions | 0:1.0-7.el7ev | | `safelease-debuginfo` | Red Hat:storage:3.4:server:el7 | All versions | 0:1.0-7.el7ev | | `vdsm` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-api` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-client` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-common` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-gluster` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-cpuflags` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-ethtool-options` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-faqemu` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-fcoe` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-localdisk` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-macspoof` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-openstacknet` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-qemucmdline` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | | `vdsm-hook-vmfex-dev` | Red Hat:storage:3.4:server:el7 | All versions | 0:4.30.18-1.0.el7rhgs | Products: Ovirt Vdsm, Redhat Gluster Storage. ## How do I fix CVE-2019-3831? Apply the vendor's patch. ## Is CVE-2019-3831 being exploited? There is no known exploitation of CVE-2019-3831 in the wild and no public exploit code. ## Other vulnerabilities in [UNKNOWN] vdsm - [CVE-2012-5518](https://insights.sbomify.com/CVE-2012-5518/): Auth bypass in vdsm (high 7.5) - [CVE-2018-10908](https://insights.sbomify.com/CVE-2018-10908/): Denial of service in vdsm (medium 6.5) - [CVE-2022-0207](https://insights.sbomify.com/CVE-2022-0207/): Race condition in vdsm (medium 4.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2019-3831 and fix it if it is affected. What it is: CVE-2019-3831 is a medium-severity vulnerability in [UNKNOWN] vdsm, published on 25 Mar 2019. It can only be exploited from the same machine or local network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2019-3831 in the wild and no public exploit code. Affected product: [UNKNOWN] vdsm. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2019-3831/ (Markdown: https://insights.sbomify.com/CVE-2019-3831/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2019-3831 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-3831 - OSV: https://osv.dev/vulnerability/CVE-2019-3831 --- From sbomify Insights: https://insights.sbomify.com/CVE-2019-3831/ Summaries are generated and may contain mistakes; the official description above is the record.