dbcve.org
Asset SuiteApplication · Hitachienergy

CVE-2023-4816

HIGH · 8.8 CVSS v3.1 Published 2023-09-11
Fix available
A fix is available. Upgrade to after 9.6.3.11.1 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
A vulnerability exists in the Equipment Tag Out authentication, when configured with Single Sign-On (SSO) with password validation in T214. This vulnerability can be exploited by an authenticated user per-forming an Equipment Tag Out holder action (Accept, Release, and Clear) for another user and entering an arbitrary password in the holder action confirmation dialog box. Despite entering an arbitrary password in the confirmation box, the system will execute the selected holder action.

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 · high confidence

In Equipment Tag Out configured with SSO and password validation in T214, the system fails to properly validate the password entered in the holder action confirmation dialog (Accept, Release, Clear). An authenticated attacker can execute holder actions for other users by entering any arbitrary password in the confirmation box, bypassing the intended password authentication checkpoint.

MitigationImplement proper server-side password validation in the Equipment Tag Out holder action confirmation workflow to ensure the entered password is correctly verified against the authenticated user's credentials before executing the action.

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
Asset SuiteApplication
Affected:<= 9.6.3.11.1= 9.6.4

CVSS 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
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Asset Suite version
    Check the installed Hitachi Energy Asset Suite version through the application UI (typically in Help > About) or check the installation directory for version files. Compare against affected versions: <= 9.6.3.11.1 or = 9.6.4
    Affected if The installed version is 9.6.3.11.1 or earlier, or exactly 9.6.4
  2. Verify Equipment Tag Out module is in use
    Access the Asset Suite system and navigate to confirm whether the Equipment Tag Out functionality is configured or available in the deployment. Check system configuration files or module listings for 'Equipment Tag Out' or 'Tag Out' components
    Affected if Equipment Tag Out module is installed and accessible in the system
  3. Confirm SSO is enabled for the system
    Check the Asset Suite system configuration or authentication settings to determine if Single Sign-On (SSO) is the configured authentication method. This is typically found in system security or authentication configuration panels
    Affected if SSO authentication is enabled for the Asset Suite application
  4. Check if password validation is enabled in T214
    Locate the T214 configuration area within the Equipment Tag Out settings. Examine whether password validation is required or enabled for holder action confirmation dialogs (Accept, Release, Clear operations)
    Affected if Password validation is enabled for holder action confirmations in T214 configuration

User is affected if running Asset Suite version <= 9.6.3.11.1 or = 9.6.4 with Equipment Tag Out configured using SSO and password validation enabled in T214.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

From vendor data
Upgrade available Upgrade to a release after 9.6.3.11.1
Interim mitigation

Implement proper server-side password validation in the Equipment Tag Out holder action confirmation workflow to ensure the entered password is correctly verified against the authenticated user's credentials before executing the action.

Fix this in Asset Suite Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-4816 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-4816 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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