# CVE-2025-3624: Missing Authorization Vulnerability in Hitachi Ops Center Analyzer

> Attackers can access restricted functionality in Hitachi Ops Center Analyzer due to missing authorization checks, potentially reading or modifying data.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N`)
- **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:** 16 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-42j6-mxwq-5g26

## What is CVE-2025-3624?

CVE-2025-3624 is a medium-severity missing authorization vulnerability in Hitachi Ops Center Analyzer, published on 16 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Missing Authorization vulnerability in Hitachi Ops Center Analyzer (Hitachi Ops Center Analyzer detail view component).This issue affects Hitachi Ops Center Analyzer: from 10.0.0-00 before 11.0.4-00.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-3624?


## How do I fix CVE-2025-3624?

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

## Is CVE-2025-3624 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-3624 and fix it if it is affected.

What it is: CVE-2025-3624 is a medium-severity missing authorization vulnerability in Hitachi Ops Center Analyzer, published on 16 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-3624 in the wild and no public exploit code.

Affected product: Hitachi Ops Center Analyzer. 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-2025-3624/ (Markdown: https://insights.sbomify.com/CVE-2025-3624/index.md)
```

## Sources

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

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