CVE-2024-47191: Local root exploit in the PAM module pam_oath.so

Published Oct 4, 2024
·
Updated

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

3 affected componentsFixes available
debian/oath-toolkit
2.6.6-32.6.7-3.1+deb12u12.6.12-1
Microsoft cbl2 oath-toolkit 2.6.7-3
Microsoft azl3 oath-toolkit 2.6.9-2

Event History

Oct 4, 2024
Data Sourced
via Red Hat·03:39 PM
DescriptionSeverityAffected Software
Oct 9, 2024
CVE Published
via MITRE·12:00 AM
Data Sourced
via MITRE·12:00 AM
Description
Data Sourced
via NVD·05:15 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·07:00 AM
Affected Software
Updated
via Microsoft·07:00 AM
DescriptionSeverity
Oct 21, 2024
Data Sourced
via Ubuntu·04:48 PM
RemedyDescriptionSeverityAffected Software

Frequently Asked Questions

1

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.

2

How do I fix CVE-2024-47191?

To fix CVE-2024-47191, upgrade to oath-toolkit version 2.6.12 or later.

3

What versions are affected by CVE-2024-47191?

CVE-2024-47191 affects oath-toolkit versions 2.6.7 through 2.6.11.

4

What does CVE-2024-47191 exploit?

CVE-2024-47191 exploits mishandling of usersfile access in PAM code running as root.

5

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203