Libvirt: swtpm privilege escalation via symlink following
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: total
Summary
A flaw was found in libvirt. A local attacker, specifically a process running as the confined `swtpm` user, could exploit a symlink-following vulnerability in the `virFileChownFiles()` function. By planting a symbolic link within the `swtpm` state directory, the attacker could trick the root-level libvirt daemon into changing the ownership of an arbitrary file to the `swtpm` user. This allows for privilege escalation from the `swtpm` sandbox to root-level file ownership control.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- libvirt
Version range not reported
- libvirt
Version range not reported
- libvirt
Version range not reported
- virt:rhel
Version range not reported
- virt:rhel
Version range not reported
- virt:rhel
Version range not reported
- virt:rhel
Version range not reported
- virt:rhel
Version range not reported
- virt:rhel
Version range not reported
- libvirt
Version range not reported
- libvirt
Version range not reported
- libvirt
Version range not reported
- libvirt
Version range not reported
- libvirt
Version range not reported
- virt:rhel/libvirt
Version range not reported
- libvirt
Version range not reported