CVE-2011-3149: The _expand_arg function in the pam_env module (modules/pam_env/pam_env.c) in Linux-PAM (aka pam) before 1.1.5 does not properly handle when…
Noroxi assessment
Priority: Monitor (action score 8/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.53% (FIRST EPSS).
- No special conditions are required; it is repeatable.
- Fixed version: pam (Debian:12) 1.1.3-5; pam (Debian:6.0) 1.1.1-6.1+squeeze1; pam (openSUSE:Tumbleweed) 1.3.0-3.4.
Low priority for now. Upgrade to pam (Debian:12) 1.1.3-5; pam (Debian:6.0) 1.1.1-6.1+squeeze1; pam (openSUSE:Tumbleweed) 1.3.0-3.4 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 _expand_arg function in the pam_env module (modules/pam_env/pam_env.c) in Linux-PAM (aka pam) before 1.1.5 does not properly handle when environment variable expansion can overflow, which allows local users to cause a denial of service (CPU consumption).
- Published
- Jul 22, 2012
- Updated
- Jun 16, 2026
- EPSS
- 0.5% · 45th percentile
- CWE
- CWE-119
Report tools
Action score
8
Low priority for now.
- CVSS
- 8 / 40 · 2.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.5%
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.4 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-5 | 1.1.3-5 |
| Debian:6.0 | pam | before 1.1.1-6.1+squeeze1 | 1.1.1-6.1+squeeze1 |
| openSUSE:Tumbleweed | pam | before 1.3.0-3.4 | 1.3.0-3.4 |
| Red Hat:enterprise_linux:6::client | pam | before 0:1.1.1-13.el6 | 0:1.1.1-13.el6 |
| Red Hat:enterprise_linux:6::client | pam-debuginfo | before 0:1.1.1-13.el6 | 0:1.1.1-13.el6 |
| Red Hat:enterprise_linux:6::client | pam-devel | before 0:1.1.1-13.el6 | 0:1.1.1-13.el6 |
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-4707Jan 24, 2011 · 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…19Monitor
- ← EarlierCVE-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
- Later →CVE-2014-2583Apr 10, 2014 · Multiple directory traversal vulnerabilities in pam_timestamp.c in the pam_timestamp module for Linux-PAM (aka pam) 1.1.8 allow local users…24Monitor
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-5 · Debian:12 | Package registry (OSV) |
| opensuse:pam | 1.3.0-3.4 · openSUSE:Tumbleweed | Package registry (OSV) |
| red hat:pam | 0:1.1.1-13.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:pam-debuginfo | 0:1.1.1-13.el6 · Red Hat:enterprise_linux:6::client | Package registry (OSV) |
| red hat:pam-devel | 0:1.1.1-13.el6 · Red Hat:enterprise_linux:6::client | 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
- none
- Integrity
- none
- Availability
- P · the service can be disrupted
- Attack complexity
- Low
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- P
Weakness class (CWE)
CWE-119 · Improper Restriction of Operations within the Bounds of a Memory BufferCVSS vector
AV:L/AC:L/Au:N/C:N/I:N/A:P
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.
Attack patterns (CAPEC)
- Buffer Overflow via Environment VariablesCAPEC-10likelihood: High · High
- Overflow BuffersCAPEC-100likelihood: High · Very High
- Buffer ManipulationCAPEC-123likelihood: High · Very High
- Client-side Injection-induced Buffer OverflowCAPEC-14likelihood: Medium · High
- Filter Failure through Buffer OverflowCAPEC-24likelihood: High · High
- MIME ConversionCAPEC-42likelihood: High · High
- Overflow Binary Resource FileCAPEC-44likelihood: High · Very High
- Buffer Overflow via Symbolic LinksCAPEC-45likelihood: High · High
ATT&CK techniques
—
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.