Skip to content
Fencer Intel
high 7.2

CVE-2010-4708 json

The pam_env module in Linux-PAM (aka pam) 1.1.2 and earlier reads the .pam_environment file in a user's home directory, which might allow l…

published 15y ago modified 4mo ago also EUVD-2010-4673

cvss
7.2
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

The pam_env module in Linux-PAM (aka pam) 1.1.2 and earlier reads the .pam_environment file in a user's home directory, which might allow local users to run programs with an unintended environment by executing a program that relies on the pam_env PAM check.

Patch / fix

  • pam Debian 14, Debian 13, Debian 12 1.1.3-7.1

debian advisories DEBIAN-CVE-2010-4708

  • pam RHEL 6 1.1.1-4.el6_0.1

red hat advisories RHSA-2010:0891

Is CVE-2010-4708 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2010-4708 updated cvss 4.6

pam: pam_env: reading ~/.pam_environment is security risk

  • Red Hat Enterprise Linux Desktop (v. 6) pam 1.1.1-4.el6_0.1 Red Hat Enterprise Linux Desktop Optional (v. 6) pam 1.1.1-4.el6_0.1 Red Hat Enterprise Linux HPC Node (v. 6) pam 1.1.1-4.el6_0.1 Red Hat Enterprise Linux HPC Node Optional (v. 6) pam 1.1.1-4.el6_0.1 Red Hat Enterprise Linux Server (v. 6) pam 1.1.1-4.el6_0.1 Red Hat Enterprise Linux Workstation (v. 6) pam 1.1.1-4.el6_0.1
    fixed: vendor fix RHSA-2010:0891
  • Red Hat Enterprise Linux 4 pam Red Hat Enterprise Linux 5 pam
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 2.0 7.2 AV:L/AC:L/Au:N/C:C/I:C/A:C

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.