# CVE-2001-1147: Information disclosure in n/a

> Local attackers can obtain other users' credentials due to a flaw in the util-linux login PAM implementation when specific modules are used.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-hc7f-gvfc-9wwx

## What is CVE-2001-1147?

CVE-2001-1147 is a high-severity vulnerability in n/a, published on 25 Jun 2002. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

## Which versions are affected by CVE-2001-1147?

It affects 1 product.


Products: Andries Brouwer Util-Linux.

## How do I fix CVE-2001-1147?

No fix has been published for CVE-2001-1147 yet. Limit exposure of the affected software until one is available.

## Is CVE-2001-1147 being exploited?

There is no known exploitation of CVE-2001-1147 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2005-2876](https://insights.sbomify.com/CVE-2005-2876/): Privilege escalation in n/a (high 7.2)
- [CVE-2001-1175](https://insights.sbomify.com/CVE-2001-1175/): Information disclosure in n/a (high 7.2)
- [CVE-2003-0094](https://insights.sbomify.com/CVE-2003-0094/): Weak cryptography in n/a (medium 5.0)
- [CVE-2004-0080](https://insights.sbomify.com/CVE-2004-0080/): Use after free in n/a (medium 5.0)
- [CVE-2006-7108](https://insights.sbomify.com/CVE-2006-7108/): Auth bypass in n/a (medium 4.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2001-1147 and fix it if it is affected.

What it is: CVE-2001-1147 is a high-severity vulnerability in n/a, published on 25 Jun 2002. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2001-1147 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2001-1147/ (Markdown: https://insights.sbomify.com/CVE-2001-1147/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2001-1147
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2001-1147
- OSV: https://osv.dev/vulnerability/CVE-2001-1147

---
From sbomify Insights: https://insights.sbomify.com/CVE-2001-1147/
Summaries are generated and may contain mistakes; the official description above is the record.