Skip to content
Fencer Intel
medium 4.7

CVE-2010-3430 json

The privilege-dropping implementation in the (1) pam_env and (2) pam_mail modules in Linux-PAM (aka pam) 1.1.2 does not perform the require…

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

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

Summary

The privilege-dropping implementation in the (1) pam_env and (2) pam_mail modules in Linux-PAM (aka pam) 1.1.2 does not perform the required setfsgid and setgroups system calls, which might allow local users to obtain sensitive information by leveraging unintended group permissions, as demonstrated by a symlink attack on the .pam_environment file in a user's home directory. NOTE: this vulnerability exists because of an incomplete fix for CVE-2010-3435.

Patch / fix

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

debian advisories DEBIAN-CVE-2010-3430

  • pam openSUSE Tumbleweed 1.3.0-3.4

opensuse advisories openSUSE-SU-2024:10405-1

Is CVE-2010-3430 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-3430 updated cvss 1.9

pam: pam_mail and pam_env incorrect privilege dropping

  • Red Hat Enterprise Linux 4 pam Red Hat Enterprise Linux 5 pam Red Hat Enterprise Linux 6 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.34% chance of exploitation in the next 30 days, higher than 27% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

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.