# CVE-2025-2500: Information disclosure in Asset Suite

> Attackers can gain unauthorized access and expand password attack windows via SOAP Web services in Hitachi Energy Asset Suite.

- **Severity:** Critical 9.1 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 May 2025
- **Updated:** 30 May 2025
- **Also known as:** GHSA-3c82-pv2c-m48j

## What is CVE-2025-2500?

CVE-2025-2500 is a critical vulnerability in Hitachi Energy Asset Suite, published on 30 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability exists in the SOAP Web services of the Asset 
Suite versions listed below. If successfully exploited, an attacker 
could gain unauthorized access to the product and the time window of a possible password attack could be expanded.

Weakness: CWE-256 (Plaintext Storage of a Password)

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


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

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

## Is CVE-2025-2500 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-2500 is a critical vulnerability in Hitachi Energy Asset Suite, published on 30 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-2500 in the wild and no public exploit code.

Affected product: Hitachi Energy Asset Suite. 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-2500/ (Markdown: https://insights.sbomify.com/CVE-2025-2500/index.md)
```

## Sources

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

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