# CVE-2024-22216: Missing authorization in n/a

> Unauthorized access in Microchip maxView Storage Manager allows attackers to modify data and disclose information via the Redfish server.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Jan 2024
- **Updated:** 18 Jun 2025
- **Also known as:** GHSA-gwr5-jm6x-gfh6

## What is CVE-2024-22216?

CVE-2024-22216 is a critical missing authorization vulnerability in n/a, published on 8 Jan 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

In default installations of Microchip maxView Storage Manager (for Adaptec Smart Storage Controllers) where Redfish server is configured for remote system management, unauthorized access can occur, with data modification and information disclosure. This affects 3.00.23484 through 4.14.00.26064 (except for the patched versions 3.07.23980 and 4.07.00.25339).

Weakness: CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-22216?

It affects 1 product.


Products: Microchip Maxview Storage Manager.

## How do I fix CVE-2024-22216?

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

## Is CVE-2024-22216 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-51438](https://insights.sbomify.com/CVE-2023-51438/): Auth bypass in SIMATIC IPC1047E (critical 10.0)
- [CVE-2023-23588](https://insights.sbomify.com/CVE-2023-23588/): Weak cryptography in SIMATIC IPC1047 (medium 6.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-22216 and fix it if it is affected.

What it is: CVE-2024-22216 is a critical missing authorization vulnerability in n/a, published on 8 Jan 2024. 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-2024-22216 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-2024-22216/ (Markdown: https://insights.sbomify.com/CVE-2024-22216/index.md)
```

## Sources

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

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