pam: pam_namespace executes namespace.init with service's environment
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| n/a | n/a | affected |
|
Configuration 1 [-]
|
| Package | CPE | Advisory | Released Date |
|---|---|---|---|
| Red Hat Enterprise Linux 5 | |||
| pam-0:0.99.6.2-6.el5_5.2 | cpe:/o:redhat:enterprise_linux:5 | RHSA-2010:0819 | 2010-11-01T00:00:00Z |
| Red Hat Enterprise Linux 6 | |||
| pam-0:1.1.1-4.el6_0.1 | cpe:/o:redhat:enterprise_linux:6 | RHSA-2010:0891 | 2010-11-16T00:00:00Z |
No data available yet.
| Source | ID | Title |
|---|---|---|
EUVD |
EUVD-2010-3832 | pam_namespace.c in the pam_namespace module in Linux-PAM (aka pam) before 1.1.3 uses the environment of the invoking application or service during execution of the namespace.init script, which might allow local users to gain privileges by running a setuid program that relies on the pam_namespace PAM check, as demonstrated by the sudo program. |
Ubuntu USN |
USN-1140-1 | PAM vulnerabilities |
No CVSS v4.0
No CVSS v3.1
No CVSS v3.0
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.412% probability within 30 days)
Key SSVC decision points have not yet been added.
No history.