In support.c in pam_tacplus 1.3.8 through 1.5.1, the TACACS+ shared secret gets logged via syslog if the DEBUG loglevel and journald are used.
Information written to log files can be of a sensitive nature and give valuable guidance to an attacker or expose sensitive user information.
Name | Vendor | Start Version | End Version |
---|---|---|---|
Pam_tacplus | Pam_tacplus_project | 1.3.8 (including) | 1.5.1 (including) |
Libpam-tacplus | Ubuntu | bionic | * |
Libpam-tacplus | Ubuntu | eoan | * |
Libpam-tacplus | Ubuntu | focal | * |
Libpam-tacplus | Ubuntu | groovy | * |
Libpam-tacplus | Ubuntu | hirsute | * |
Libpam-tacplus | Ubuntu | impish | * |
Libpam-tacplus | Ubuntu | kinetic | * |
Libpam-tacplus | Ubuntu | lunar | * |
Libpam-tacplus | Ubuntu | mantic | * |
Libpam-tacplus | Ubuntu | trusty | * |
Libpam-tacplus | Ubuntu | xenial | * |
While logging all information may be helpful during development stages, it is important that logging levels be set appropriately before a product ships so that sensitive user data and system information are not accidentally exposed to potential attackers. Different log files may be produced and stored for: