Root privilege escalation via symlink-following usersfile writes
Published Oct 9, 2024 · Updated Oct 18, 2024
Local privilege escalation in OATH Toolkit 2.6.7 through 2.6.11 allows local users to obtain root privileges via a crafted symlink. When pam_oath.so processes a usersfile under an unprivileged home directory, oath_authenticate_usersfile() follows a preplaced .new symlink and uses root privileges to overwrite and fchown its target. The PAM stack must run as root with a ${HOME}-expanded usersfile path, and no race is required to replace a root-owned file and take full control.
Summary
What happened
Local privilege escalation in OATH Toolkit 2.6.7 through 2.6.11 allows local users to obtain root privileges via a crafted symlink. When pam_oath.so processes a usersfile under an unprivileged home directory, oath_authenticate_usersfile() follows a preplaced .new symlink and uses root privileges to overwrite and fchown its target. The PAM stack must run as root with a ${HOME}-expanded usersfile path, and no race is required to replace a root-owned file and take full control.
The record
- CVE
- CVE-2024-47191
- Published
- Oct 9, 2024
- Updated
- Oct 18, 2024
- Vendor
- OATH Toolkit
- Product
- OATH Toolkit
- Classifications
- CWE-22, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Oct 9, 2024CVE publishedPublication date reported by the CVE source.
- Oct 18, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.6.7 <2.6.12
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- SUSE usersfile symlink proof of conceptproof of concept · 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