CVE-2025-5781
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInformation Exposure Vulnerability in Hitachi Ops Center API Configuration Manager, Hitachi Configuration Manager, Hitachi Device Manager allows Session Hijacking.This issue affects Hitachi Ops Center API Configuration Manager: from 10.0.0-00 before 11.0.5-00; Hitachi Configuration Manager: from 8.5.1-00 before 11.0.5-00; Hitachi Device Manager: from 8.4.1-00 before 8.6.5-00.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAn information exposure vulnerability in Hitachi Ops Center API Configuration Manager, Hitachi Configuration Manager, and Hitachi Device Manager allows authenticated attackers to intercept or hijack user sessions. The vulnerability stems from improper handling of session data or authentication tokens within the API Configuration Manager component, potentially exposing session credentials that can be reused to impersonate legitimate users.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 8.5.1-00>= 8.5.1-00, < 11.0.5-00>= 8.4.1-00, < 8.6.5-00>= 10.0.0-00, < 11.0.5-00CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed Hitachi Configuration Manager versionCheck the product version through the management console or by running: /opt/hitachi/hcm/bin/hcmversion (or consult the program's About/Version information in the GUI)Affected if Installed version is 8.5.1-00 or higher but below 11.0.5-00
-
Identify installed Hitachi Device Manager versionCheck the product version through the management console or by running: /opt/hitachi/hdm/bin/hdmversion (or consult the program's About/Version information in the GUI)Affected if Installed version is 8.4.1-00 or higher but below 8.6.5-00
-
Identify installed Hitachi Ops Center API Configuration Manager versionCheck the product version through Ops Center administration portal or by querying the API Configuration Manager service version endpointAffected if Installed version is 10.0.0-00 or higher but below 11.0.5-00
-
Verify if API Configuration Manager component is enabledAccess the Ops Center administration console and navigate to the API Configuration Manager component section, or query the component status via the API: GET /api/v1/components or check service statusAffected if API Configuration Manager component is running and accessible via network
-
Check for session token exposure in logs or API responsesReview API Configuration Manager logs (typically in /opt/hitachi/ocapicm/logs/ or the product's log directory) and capture API responses to identify if session tokens or authentication credentials are being returned in responses or written to logsAffected if Session tokens, authentication credentials, or session identifiers appear in API responses or are logged in plaintext
You are affected if any of the three products is running a vulnerable version (as listed above) AND the API Configuration Manager component is enabled and accessible on the network, allowing potential interception of session data.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped8.6.5-0011.0.5-00
Upgrade Hitachi Ops Center API Configuration Manager and Configuration Manager to version 11.0.5-00 or later, and Hitachi Device Manager to version 8.6.5-00 or later to remediate this vulnerability.
Configuration Manager: upgrade to 11.0.5-00 or later; Device Manager: upgrade to 8.6.5-00 or later; Ops Center API Configuration Manager: upgrade to 11.0.5-00 or later
- Identify which Hitachi product(s) are affected in your environment: Configuration Manager, Device Manager, or Ops Center API Configuration Manager
- Review current version to confirm it falls within affected range (Configuration Manager: 8.5.1-00 to 11.0.5-00, Device Manager: 8.4.1-00 to 8.6.5-00, Ops Center API Configuration Manager: 10.0.0-00 to 11.0.5-00)
- Schedule a maintenance window for the upgrade
- Backup current configuration and any custom settings
- For Configuration Manager and Ops Center API Configuration Manager: Upgrade to version 11.0.5-00 or later
- For Device Manager: Upgrade to version 8.6.5-00 or later
- Verify the upgrade was successful by checking product version
- Validate that the application starts without errors
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-5781 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-5781 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data