# CVE-2022-22411: Privilege escalation in Spectrum Scale DAS

> An authenticated user can exploit excessive permissions to insert code and manipulate cluster resources in IBM Spectrum Scale Data Access Services.

- **Severity:** Medium 6.3 (`CVSS:3.0/I:H/PR:L/S:C/AV:N/A:N/UI:N/C:N/AC:H/E:U/RL:O/RC: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:** 10 Aug 2022
- **Updated:** 17 Sep 2024
- **Also known as:** GHSA-hqh2-45gr-jc64

## What is CVE-2022-22411?

CVE-2022-22411 is a medium-severity vulnerability in IBM Spectrum Scale DAS, published on 10 Aug 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

IBM Spectrum Scale Data Access Services (DAS) 5.1.3.1 could allow an authenticated user to insert code which could allow the attacker to manipulate cluster resources due to excessive permissions. IBM X-Force ID: 223016.

Weakness: CWE-732 (Incorrect Permission Assignment for Critical Resource)

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

It affects 1 product.


Products: Ibm Spectrum Scale Data Access Services.

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

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

## Is CVE-2022-22411 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-22411 is a medium-severity vulnerability in IBM Spectrum Scale DAS, published on 10 Aug 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-22411 in the wild and no public exploit code.

Affected product: IBM Spectrum Scale DAS. 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-22411/ (Markdown: https://insights.sbomify.com/CVE-2022-22411/index.md)
```

## Sources

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

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