CVE-2010-4707: The check_acl function in pam_xauth.c in the pam_xauth module in Linux-PAM (aka pam) 1.1.2 and earlier does not verify that a certain ACL…
Noroxi assessment
Priority: Monitor (action score 19/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.36% (FIRST EPSS).
- No special conditions are required; it is repeatable.
- Fixed version: pam (Debian:12) 1.1.3-1; pam (Red Hat:enterprise_linux:5::client_workstation) 0:0.99.6.2-6.el5_5.2; pam-debuginfo (Red Hat:enterprise_linux:5::client_workstation) 0:0.99.6.2-6.el5_5.2.
Low priority for now. Upgrade to pam (Debian:12) 1.1.3-1; pam (Red Hat:enterprise_linux:5::client_workstation) 0:0.99.6.2-6.el5_5.2; pam-debuginfo (Red Hat:enterprise_linux:5::client_workstation) 0:0.99.6.2-6.el5_5.2 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
The check_acl function in pam_xauth.c in the pam_xauth module in Linux-PAM (aka pam) 1.1.2 and earlier does not verify that a certain ACL file is a regular file, which might allow local users to cause a denial of service (resource consumption) via a special file.
- Published
- Jan 24, 2011
- Updated
- Jun 16, 2026
- EPSS
- 0.3% · 30th percentile
- CWE
- CWE-399
Report tools
Action score
19
Low priority for now.
- CVSS
- 19 / 40 · 4.9 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.3%
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| linux-pam | linux-pam | cpe:2.3:a:linux-pam:linux-pam |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- linux-pam linux-pamup to 1.1.2 inclusive
- linux-pam linux-pam0.99.1.0
- linux-pam linux-pam0.99.10.0
- linux-pam linux-pam0.99.2.0
- linux-pam linux-pam0.99.2.1
- linux-pam linux-pam0.99.3.0
- linux-pam linux-pam0.99.4.0
- linux-pam linux-pam0.99.5.0
+12 more rows
- linux-pam linux-pam0.99.6.0
- linux-pam linux-pam0.99.6.1
- linux-pam linux-pam0.99.6.2
- linux-pam linux-pam0.99.6.3
- linux-pam linux-pam0.99.7.0
- linux-pam linux-pam0.99.7.1
- linux-pam linux-pam0.99.8.0
- linux-pam linux-pam0.99.8.1
- linux-pam linux-pam0.99.9.0
- linux-pam linux-pam1.0.0
- linux-pam linux-pam1.0.1
- linux-pam linux-pam1.0.2
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Debian:12 | pam | before 1.1.3-1 | 1.1.3-1 |
| Red Hat:enterprise_linux:5::client_workstation | pam | before 0:0.99.6.2-6.el5_5.2 | 0:0.99.6.2-6.el5_5.2 |
| Red Hat:enterprise_linux:5::client_workstation | pam-debuginfo | before 0:0.99.6.2-6.el5_5.2 | 0:0.99.6.2-6.el5_5.2 |
| Red Hat:enterprise_linux:5::client_workstation | pam-devel | before 0:0.99.6.2-6.el5_5.2 | 0:0.99.6.2-6.el5_5.2 |
| Red Hat:enterprise_linux:6::client | pam | before 0:1.1.1-4.el6_0.1 | 0:1.1.1-4.el6_0.1 |
| Red Hat:enterprise_linux:6::client | pam-debuginfo | before 0:1.1.1-4.el6_0.1 | 0:1.1.1-4.el6_0.1 |
| Red Hat:enterprise_linux:6::client | pam-devel | before 0:1.1.1-4.el6_0.1 | 0:1.1.1-4.el6_0.1 |
Same product
linux-pam: all recordsOther highest-scoring records for the same primary product.
- CVE-2020-27780A flaw was found in Linux-Pam in versions prior to 1.5.1 in the way it handle empty passwords for non-existing users.40Plan
- CVE-2022-28321The Linux-PAM package before 1.5.2-6.1 for openSUSE Tumbleweed allows authentication bypass for SSH logins.39Monitor
- CVE-2010-4708The 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…28Monitor
Published before and after this one in the same product
- ← EarlierCVE-2010-3853Jan 24, 2011 · 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…27Monitor
- ← EarlierCVE-2010-4706Jan 24, 2011 · The pam_sm_close_session function in pam_xauth.c in the pam_xauth module in Linux-PAM (aka pam) 1.1.2 and earlier does not properly handle…19Monitor
- Later →CVE-2011-3148Jul 22, 2012 · Stack-based buffer overflow in the _assemble_line function in modules/pam_env/pam_env.c in Linux-PAM (aka pam) before 1.1.5 allows local…18Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| debian:pam | 1.1.3-1 · Debian:12 | Package registry (OSV) |
| red hat:pam | 0:0.99.6.2-6.el5_5.2 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:pam-debuginfo | 0:0.99.6.2-6.el5_5.2 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
| red hat:pam-devel | 0:0.99.6.2-6.el5_5.2 · Red Hat:enterprise_linux:5::client_workstation | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
Not on record for this CVE: EPSS history · patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- C · data can be read
- Integrity
- none
- Availability
- none
- Attack complexity
- Low
- Confidentiality impact
- C
- Integrity impact
- None
- Availability impact
- None
Weakness class (CWE)
CWE-399 · Resource Management ErrorsCVSS vector
AV:L/AC:L/Au:N/C:C/I:N/A:N
nvd-primary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
MITRE has no CAPEC/ATT&CK mapping for this CWE.
Change log (1)
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (5 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.