# CVE-2024-22385: File and Directory Permission Vulnerability in Hitachi Storage Provider for VMware vCenter

> Local users can read and write specific files due to incorrect default permissions in Hitachi Storage Provider for VMware vCenter.

- **Severity:** Medium 4.4 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-xjph-r444-9j84

## What is CVE-2024-22385?

CVE-2024-22385 is a medium-severity vulnerability in Hitachi Storage Provider for VMware vCenter, published on 25 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Incorrect Default Permissions vulnerability in Hitachi Storage Provider for VMware vCenter allows local users to read and write specific files.This issue affects Hitachi Storage Provider for VMware vCenter: from 3.1.0 before 3.7.4.

Weakness: CWE-276 (Incorrect Default Permissions)

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


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

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

## Is CVE-2024-22385 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-22385 is a medium-severity vulnerability in Hitachi Storage Provider for VMware vCenter, published on 25 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-22385 in the wild and no public exploit code.

Affected product: Hitachi Storage Provider for VMware vCenter. 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-22385/ (Markdown: https://insights.sbomify.com/CVE-2024-22385/index.md)
```

## Sources

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

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