CVE-2001-1147 json
The PAM implementation in /bin/login of the util-linux package before 2.11 causes a password entry to be rewritten across multiple PAM call…
published 2001-10-08 25 y ago modified 2026-06-16 4 mo ago also EUVD-2001-1128
- 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 37%
- public exploits
- 0
- none known
Summary
The PAM implementation in /bin/login of the util-linux package before 2.11 causes a password entry to be rewritten across multiple PAM calls, which could provide the credentials of one user to a different user, when used in certain PAM modules such as pam_limits.
Patch / fix
- iss.net/security_center/static/7266.php advisory
- securityfocus.com/bid/3415 advisory
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-2001-1147 updated
security flaw
-
Red Hat Linux 7.1 Red Hat Linux 7.2fixed: vendor fix RHSA-2001:132
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.43% chance of exploitation in the next 30 days, higher than 37% of all scored CVEs (FIRST EPSS, 2026-11-08).
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
-
iss.net
/security_center/static/7266.php
vdb-entry, patch, vendor-advisory
-
securityfocus.com
/bid/3415
vdb-entry, patch, vendor-advisory
-
redhat.com
/support/errata/RHSA-2001-132.html
vendor-advisory
-
novell.com
/linux/security/advisories/2001_034_shadow_txt.html
vendor-advisory
-
linux-mandrake.com
/en/security/2001/MDKSA-2001-084.php3
vendor-advisory
-
securityfocus.com
/archive/1/219175
mailing-list, vendor-advisory
-
ciac.org
/ciac/bulletins/m-009.shtml
third-party-advisory, government-resource
Sources
- CVE List CVE-2001-1147
- NVD CVE-2001-1147
Fencer Vulns 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.