pam_usb: Thread-unsafe static pointer in log.c causes data race under concurrent PAM authentication
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| mcdope | pam_usb | affected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mcdope | Pam Usb |
|
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.116% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Mcdope
Mcdope pam Usb |
|
| Vendors & Products |
Mcdope
Mcdope pam Usb |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | pam_usb provides hardware authentication for Linux using ordinary removable media. Prior to 0.9.1, src/log.c contains a process-wide static pointer that is written on every PAM invocation with the address of a stack-local variable. This violates the PAM re-entrancy requirement and creates a data race when the PAM stack is invoked concurrently from multiple threads. This vulnerability is fixed in 0.9.1. | |
| Title | pam_usb: Thread-unsafe static pointer in log.c causes data race under concurrent PAM authentication | |
| Weaknesses | CWE-362 CWE-476 |
|
| References |
| |
| Metrics |
cvssV3_1
|