CVE-2019-10166
CVE-2019-10166 Vulnerability Analysis & Exploit Intelligence
It was discovered that libvirtd, versions 4.x.x before 4.10.1 and 5.x.x before 5.4.1, would permit readonly clients to use the virDomainManagedSaveDefineXML() API, which would permit them to modify managed save state files. If a managed save had already been created by a privileged user, a local attacker could modify this file such that libvirtd would execute an arbitrary program when the domain was resumed.
Published Updated Sources: cvelistV5, redhat
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
chance of exploitation in 30 days
CVSS base
7.8
HIGH
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.8 | CVSS 3.0 | HIGH | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-284
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
- T1027.009Obfuscated Files or Information: Embedded Payloads
- T1546.004Event Triggered Execution: .bash_profile and .bashrc
- T1546.016Event Triggered Execution: Installer Packages
References
3 on the record
- access.redhat.com/libvirt-privesc-vulnerabilities
x_refsource_CONFIRM
- bugzilla.redhat.com/show_bug.cgi?id=CVE-2019-10166
x_refsource_CONFIRM
- security.gentoo.org/glsa/202003-18
vendor-advisory, x_refsource_GENTOO
Elsewhere on this site
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.