# CVE-2022-24551: Auth bypass in n/a

> Attackers can reset any local user password, including administrators, due to missing validation of current credentials in StarWind SAN and NAS.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 6 Feb 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-gfwj-v75f-c948

## What is CVE-2022-24551?

CVE-2022-24551 is a high-severity authentication bypass vulnerability in n/a, published on 6 Feb 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A flaw was found in StarWind Stack. The endpoint for setting a new password doesn’t check the current username and old password. An attacker could reset any local user password (including system/administrator user) using any available user This affects StarWind SAN and NAS v0.2 build 1633.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-24551?

It affects 2 products.


Products: Starwindsoftware Nas, Starwindsoftware San.

## How do I fix CVE-2022-24551?

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

## Is CVE-2022-24551 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2022-24552](https://insights.sbomify.com/CVE-2022-24552/): Command injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24551 and fix it if it is affected.

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

## Sources

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

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