# CVE-2025-1531: Authentication credentials leakage vulnerability in Hitachi Ops Center Analyzer viewpoint OVF

> Attackers can leak authentication credentials from Hitachi Ops Center Analyzer viewpoint, potentially compromising system access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 May 2025
- **Updated:** 16 May 2025
- **Also known as:** GHSA-p7j8-2rgx-mwxm

## What is CVE-2025-1531?

CVE-2025-1531 is a medium-severity vulnerability in Hitachi Ops Center Analyzer viewpoint, published on 16 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Authentication credentials leakage  vulnerability in Hitachi Ops Center Analyzer viewpoint.This issue affects Hitachi Ops Center Analyzer viewpoint: from 10.0.0-00 before 11.0.4-00.

Weakness: CWE-1392 (Use of Default Credentials)

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


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

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

## Is CVE-2025-1531 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1531 is a medium-severity vulnerability in Hitachi Ops Center Analyzer viewpoint, published on 16 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1531 in the wild and no public exploit code.

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

## Sources

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

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