# CVE-2009-2410: Auth bypass in n/a

> Attackers can bypass authentication and gain access to accounts with blank passwords by providing any password during SSH login.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jul 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-w98w-3mj2-7wj3

## What is CVE-2009-2410?

CVE-2009-2410 is a high-severity authentication bypass vulnerability in n/a, published on 30 Jul 2009. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The local_handler_callback function in server/responder/pam/pam_LOCAL_domain.c in sssd 0.4.1 does not properly handle blank-password accounts in the SSSD BE database, which allows context-dependent attackers to obtain access by sending the account's username, in conjunction with an arbitrary password, over an ssh connection.

Weakness: CWE-287 (Improper Authentication)

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

It affects 1 product.


Products: Fedorahosted Sssd.

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

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

## Is CVE-2009-2410 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2010-4341](https://insights.sbomify.com/CVE-2010-4341/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2009-2410 is a high-severity authentication bypass vulnerability in n/a, published on 30 Jul 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-2410 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-2410/ (Markdown: https://insights.sbomify.com/CVE-2009-2410/index.md)
```

## Sources

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

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