# CVE-2022-34453: Missing authorization in XtremIO X2

> Remote read-only users can modify QoS policies in Dell XtremIO XMS if the feature is enabled, requiring an upgrade to fix.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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:** 3 Aug 2023
- **Updated:** 15 Oct 2024
- **Also known as:** GHSA-8h5q-7fj7-x2rp

## What is CVE-2022-34453?

CVE-2022-34453 is a high-severity missing authorization vulnerability in Dell XtremIO X2 , published on 3 Aug 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Dell XtremIO X2 XMS versions prior to 6-4-1.11 contain an improper access control vulnerability. A remote read only user could potentially exploit this vulnerability to perform add/delete QoS policies which are disabled by default.

Weakness: CWE-284 (Improper Access Control)

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

It affects 1 product.


Products: Dell Xtremio X2 Firmware.

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

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

## Is CVE-2022-34453 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-34453 is a high-severity missing authorization vulnerability in Dell XtremIO X2 , published on 3 Aug 2023. 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-34453 in the wild and no public exploit code.

Affected product: Dell XtremIO X2 . 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-34453/ (Markdown: https://insights.sbomify.com/CVE-2022-34453/index.md)
```

## Sources

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

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