Home
» Security vulnerabilities
» CVE-2019-3831
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.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2019-3831
Conclusion & alert: CVE-2019-3831 is rated Moderate Risk (48.4/100) : CVSS Medium severity, with medium exploitation likelihood (EPSS 1.03%).Mandatory action: Review affected assets and schedule remediation.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Exploit prediction scoring system (EPSS) score for CVE-2019-3831
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2026-06-15
0.10%
1.03%
+0.93%
2
2025-03-30
0.17%
0.10%
-0.07%
3
2025-03-29
—
0.17%
—
Full EPSS history
(9 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2019-3831
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
6.7
3.1
MEDIUM
CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
0.8
5.9
[email protected]
6.4
3.0
MEDIUM
CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:H)
They need powerful rights—admin, root, or similar—before this pays off.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
0.5
5.9
[email protected]
9.0
2.0
HIGH
AV:N/AC:L/Au:S/C:C/I:C/A:C
Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
8.0
10.0
[email protected]
Weakness enumeration for CVE-2019-3831
OS Trackers for CVE-2019-3831
Affected software / configurations for CVE-2019-3831
Vendor
Product
Version
Raw CPE
ovirt
vdsm
>= 4.19, <= 4.30.3
cpe:2.3:a:ovirt:vdsm:*:*:*:*:*:*:*:*
ovirt
vdsm
>= 4.30.5, <= 4.30.8
cpe:2.3:a:ovirt:vdsm:*:*:*:*:*:*:*:*
redhat
gluster_storage
3.0
cpe:2.3:a:redhat:gluster_storage:3.0:*:*:*:*:*:*:*
References for CVE-2019-3831
cvelogic
Threat Intelligence