# CVE-2023-30910: Other in HPE MSA Controller

> Remote attackers can exploit inconsistent HTTP request interpretation in HPE MSA Controllers to bypass security controls.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 9 Oct 2023
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-q68p-h2v7-5w73

## What is CVE-2023-30910?

CVE-2023-30910 is a medium-severity vulnerability in Hewlett Packer Enterprise (HPE) HPE MSA Controller, published on 9 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

HPE MSA Controller prior to version IN210R004 could be remotely exploited to allow inconsistent interpretation of HTTP requests.

Weakness: CWE-444 (Inconsistent Interpretation of HTTP Requests)

## Which versions are affected by CVE-2023-30910?

It affects 3 products.


Products: Hpe Msa 1060 Storage Firmware, Hpe Msa 2060 Storage Firmware, Hpe Msa 2062 Storage Firmware.

## How do I fix CVE-2023-30910?

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

## Is CVE-2023-30910 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-30910 and fix it if it is affected.

What it is: CVE-2023-30910 is a medium-severity vulnerability in Hewlett Packer Enterprise (HPE) HPE MSA Controller, published on 9 Oct 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2023-30910 in the wild and no public exploit code.

Affected product: Hewlett Packer Enterprise (HPE) HPE MSA Controller. 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-2023-30910/ (Markdown: https://insights.sbomify.com/CVE-2023-30910/index.md)
```

## Sources

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

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