Local root escalation via symlinked object creation
Published Oct 29, 2022 · Updated Aug 3, 2024
Symlink following in multipathd in multipath-tools 0.7.7 through 0.9.x before 0.9.2 allows local users to create objects as root. The root-running mark_failed_wwid() path creation follows attacker-controlled symlinks under /dev/shm, placing a fixed-name file or directory at a chosen location. Access to /dev/shm is required, and root escalation depends on chaining this location-only write with additional vulnerable behavior.
Summary
What happened
Symlink following in multipathd in multipath-tools 0.7.7 through 0.9.x before 0.9.2 allows local users to create objects as root. The root-running mark_failed_wwid() path creation follows attacker-controlled symlinks under /dev/shm, placing a fixed-name file or directory at a chosen location. Access to /dev/shm is required, and root escalation depends on chaining this location-only write with additional vulnerable behavior.
The record
- CVE
- CVE-2022-41973
- Published
- Oct 29, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-59, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 29, 2022CVE publishedPublication date reported by the CVE source.
- Aug 3, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Leeloo Multipath symlink attack demonstrationfunctional · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo