# CVE-2024-8201: Cross-Site WebSocket Hijacking Vulnerability in Hitachi Ops Center Analyzer

> Attackers can hijack WebSocket connections in Hitachi Ops Center Analyzer to perform unauthorized actions or access sensitive data.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 16 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-c398-4r23-x3c7

## What is CVE-2024-8201?

CVE-2024-8201 is a medium-severity vulnerability in Hitachi Ops Center Analyzer, published on 16 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-Site WebSocket Hijacking vulnerability in Hitachi Ops Center Analyzer (RAID Agent component).This issue affects Hitachi Ops Center Analyzer: from 10.8.0-00 before 11.0.4-00; Hitachi Ops Center Analyzer: from 10.9.0-00 before 11.0.4-00.

Weakness: CWE-1385 (Missing Origin Validation in WebSockets)

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


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

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

## Is CVE-2024-8201 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8201 is a medium-severity vulnerability in Hitachi Ops Center Analyzer, published on 16 May 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-8201 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-2024-8201/ (Markdown: https://insights.sbomify.com/CVE-2024-8201/index.md)
```

## Sources

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

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