Yubico Pam U2f
By the Year
In 2024 there have been 0 vulnerabilities in Yubico Pam U2f . Pam U2f did not have any published security vulnerabilities last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2024 | 0 | 0.00 |
| 2023 | 0 | 0.00 |
| 2022 | 0 | 0.00 |
| 2021 | 1 | 6.80 |
| 2020 | 0 | 0.00 |
| 2019 | 2 | 7.80 |
| 2018 | 0 | 0.00 |
It may take a day or so for new Pam U2f vulnerabilities to show up in the stats or in the list of recent security vulnerabilties. Additionally vulnerabilities may be tagged under a different product or component name.
Recent Yubico Pam U2f Security Vulnerabilities
Yubico pam-u2f before 1.1.1 has a logic issue
CVE-2021-31924
6.8 - Medium
- May 26, 2021
Yubico pam-u2f before 1.1.1 has a logic issue that, depending on the pam-u2f configuration and the application used, could lead to a local PIN bypass. This issue does not allow user presence (touch) or cryptographic signature verification to be bypassed, so an attacker would still need to physically possess and interact with the YubiKey or another enrolled authenticator. If pam-u2f is configured to require PIN authentication, and the application using pam-u2f allows the user to submit NULL as the PIN, pam-u2f will attempt to perform a FIDO2 authentication without PIN. If this authentication is successful, the PIN requirement is bypassed.
authentification
Yubico pam-u2f 1.0.7 attempts parsing of the configured authfile (default $HOME/.config/Yubico/u2f_keys) as root (unless openasuser was enabled), and does not properly verify
CVE-2019-12209
7.5 - High
- June 04, 2019
Yubico pam-u2f 1.0.7 attempts parsing of the configured authfile (default $HOME/.config/Yubico/u2f_keys) as root (unless openasuser was enabled), and does not properly verify that the path lacks symlinks pointing to other files on the system owned by root. If the debug option is enabled in the PAM configuration, part of the file contents of a symlink target will be logged, possibly revealing sensitive information.
insecure temporary file
In Yubico pam-u2f 1.0.7, when configured with debug and a custom debug log file is set using debug_file
CVE-2019-12210
8.1 - High
- June 04, 2019
In Yubico pam-u2f 1.0.7, when configured with debug and a custom debug log file is set using debug_file, that file descriptor is not closed when a new process is spawned. This leads to the file descriptor being inherited into the child process; the child process can then read from and write to it. This can leak sensitive information and also, if written to, be used to fill the disk or plant misinformation.
Stay on top of Security Vulnerabilities
Want an email whenever new vulnerabilities are published for Yubico Pam U2f or by Yubico? Click the Watch button to subscribe.
