# CVE-2025-10217: Other in Asset Suite

> Authenticated users can manipulate performance log data or inject crafted entries, potentially enabling further attacks in Hitachi Energy Asset Suite.

- **Severity:** Medium 6.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA: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:** 30 Sep 2025
- **Updated:** 28 Oct 2025
- **Also known as:** GHSA-88x2-3rjx-jxpr

## What is CVE-2025-10217?

CVE-2025-10217 is a medium-severity vulnerability in Hitachi Energy Asset Suite, published on 30 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability exists in Asset Suite for an authenticated user to manipulate the content of performance related log data or to inject crafted data in logfile for potentially carrying out further malicious attacks. Performance logging is typically enabled for troubleshooting purposes while resolving application performance related issues.

Weakness: CWE-117 (Improper Output Neutralization for Logs)

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


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

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

## Is CVE-2025-10217 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-10217 is a medium-severity vulnerability in Hitachi Energy Asset Suite, published on 30 Sep 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-10217 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-10217/ (Markdown: https://insights.sbomify.com/CVE-2025-10217/index.md)
```

## Sources

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

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