# CVE-2009-1384: Information disclosure in n/a

> Remote attackers can enumerate valid usernames by observing differing password prompts in the pam_krb5 module.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 May 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7qjh-v92x-xj4g, RHSA-2010:0258

## What is CVE-2009-1384?

CVE-2009-1384 is a medium-severity vulnerability in n/a, published on 28 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

pam_krb5 2.2.14 through 2.3.4, as used in Red Hat Enterprise Linux (RHEL) 5, generates different password prompts depending on whether the user account exists, which allows remote attackers to enumerate valid usernames.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2009-1384?

It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pam_krb5` | Red Hat:enterprise_linux:5::client | All versions | 0:2.2.14-15 |
| `pam_krb5-debuginfo` | Red Hat:enterprise_linux:5::client | All versions | 0:2.2.14-15 |
| `pam_krb5` | Red Hat:enterprise_linux:5::server | All versions | 0:2.2.14-15 |
| `pam_krb5-debuginfo` | Red Hat:enterprise_linux:5::server | All versions | 0:2.2.14-15 |

Products: Eyrie Pam-Krb5.

## How do I fix CVE-2009-1384?

Apply the vendor's patch.

## Is CVE-2009-1384 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2009-0360](https://insights.sbomify.com/CVE-2009-0360/): Privilege escalation in n/a (medium 6.2)
- [CVE-2009-0361](https://insights.sbomify.com/CVE-2009-0361/): Privilege escalation in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2009-1384 and fix it if it is affected.

What it is: CVE-2009-1384 is a medium-severity vulnerability in n/a, published on 28 May 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2009-1384 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-2009-1384/ (Markdown: https://insights.sbomify.com/CVE-2009-1384/index.md)
```

## Sources

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

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