CVE-2024-47191: Local root exploit in the PAM module pam_oath.so
Last updated 17 October 2024
Other sources
oath-toolkit[1] contains libraries and utilities for managing one-time password (OTP) authentication e.g. as a second factor to password authentication. A couple of years ago, the module gained a feature which allows to place the OTP state file (called usersfile) in the home directory of the to-be-authenticated user. Fabian noticed that the PAM module performs unsafe file operations in users' home directories. Since PAM stacks typically run as root, this can easily cause security issues.
The feature in question has been introduced in oath-toolkit version 2.6.7 (via commit 60d9902b5c [2]). The following report is based on the most recent oath-toolkit release tag for version 2.6.11.
— Red Hat
pamoath.so in oath-toolkit 2.6.7 through 2.6.11 before 2.6.12 allows root privilege escalation because in the context of PAM code running as root it mishandles usersfile access such as by calling fchown in the presence of a symlink.
— Microsoft
pamoath.so in oath-toolkit 2.6.7 through 2.6.11 before 2.6.12 allows root privilege escalation because, in the context of PAM code running as root, it mishandles usersfile access, such as by calling fchown in the presence of a symlink.
— NVD
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2024-47191?
CVE-2024-47191 is classified as a high-severity vulnerability due to its potential for root privilege escalation.
How do I fix CVE-2024-47191?
To fix CVE-2024-47191, upgrade to oath-toolkit version 2.6.12 or later.
What versions are affected by CVE-2024-47191?
CVE-2024-47191 affects oath-toolkit versions 2.6.7 through 2.6.11.
What does CVE-2024-47191 exploit?
CVE-2024-47191 exploits mishandling of usersfile access in PAM code running as root.
Who is impacted by CVE-2024-47191?
Any system utilizing oath-toolkit versions 2.6.7 to 2.6.11 that run PAM code may be impacted by CVE-2024-47191.