# CVE-2010-0833: Auth bypass in n/a

> Remote attackers can bypass authentication for expired Likewise Security Authority accounts by exploiting a flaw in the pam_lsass library's password logic.

- **Severity:** Critical 9.3 (`AV:N/AC:M/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Jul 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9p5c-9rhf-4q9x

## What is CVE-2010-0833?

CVE-2010-0833 is a critical authentication bypass vulnerability in n/a, published on 27 Jul 2010. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The pam_lsass library in Likewise Open 5.4 and CIFS 5.4 before build 8046, and 6.0 before build 8234, as used in HP StorageWorks X9000 Network Storage Systems and possibly other products, uses "SetPassword logic" when running as part of a root service, which allows remote attackers to bypass authentication for a Likewise Security Authority (lsassd) account whose password is marked as expired.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2010-0833?

It affects 2 products.


Products: Likewise Likewise Cifs, Likewise Likewise Open.

## How do I fix CVE-2010-0833?

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

## Is CVE-2010-0833 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-0833 and fix it if it is affected.

What it is: CVE-2010-0833 is a critical authentication bypass vulnerability in n/a, published on 27 Jul 2010. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2010-0833 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-2010-0833/ (Markdown: https://insights.sbomify.com/CVE-2010-0833/index.md)
```

## Sources

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

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