# CVE-2023-5808: Missing authorization in System Management Unit (SMU)

> Authenticated storage administrators can access restricted configuration and diagnostic data via URL manipulation, leading to information disclosure.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:L`)
- **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:** 4 Dec 2023
- **Updated:** 28 Aug 2024
- **Also known as:** GHSA-4738-qhxm-3p4q

## What is CVE-2023-5808?

CVE-2023-5808 is a high-severity missing authorization vulnerability in Hitachi Vantara System Management Unit (SMU), published on 4 Dec 2023. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SMU versions prior to 14.8.7825.01 are susceptible to unintended information disclosure, through URL manipulation. Authenticated users in a Storage administrative role are able to access HNAS configuration backup and diagnostic data, that would normally be barred to that specific administrative role.

Weakness: CWE-287 (Improper Authentication), CWE-285 (Improper Authorization)

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

It affects 1 product.


Products: Hitachi Vantara Hitachi Network Attached Storage.

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

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

## Is CVE-2023-5808 being exploited?

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

Public exploit code:

- https://github.com/Arszilla/CVE-2023-5808 (github_poc): https://github.com/Arszilla/CVE-2023-5808

## Fix prompt for AI coding agents

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

What it is: CVE-2023-5808 is a high-severity missing authorization vulnerability in Hitachi Vantara System Management Unit (SMU), published on 4 Dec 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-2023-5808 in the wild and no public exploit code.

Affected product: Hitachi Vantara System Management Unit (SMU). 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-5808/ (Markdown: https://insights.sbomify.com/CVE-2023-5808/index.md)
```

## Sources

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

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