dbcve.org
Lumada Asset Performance ManagementApplication · Hitachienergy

CVE-2022-2155

HIGH · 7.1 CVSS v3.1 Published 2023-01-12
Fix available
A fix is available. Upgrade to 6.4.0.1 or later.
See remediation →
77/100
Remediation priority · High
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 affected versions of Lumada APM’s User Asset Group feature due to a flaw in access control mechanism implementation on the “Limited Engineer” role, granting it access to the embedded Power BI reports feature. An attacker that manages to exploit the vulnerability on a customer’s Lumada APM could access unauthorized information by gaining unauthorized access to any Power BI reports installed by the customer.  Furthermore, the vulnerability enables an attacker to manipulate asset issue comments on assets, which should not be available to the attacker. Affected versions * Lumada APM on-premises version 6.0.0.0 - 6.4.0.* List of CPEs:  * cpe:2.3:a:hitachienergy:lumada_apm:6.0.0.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:lumada_apm:6.1.0.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:lumada_apm:6.2.0.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:lumada_apm:6.3.0.0:*:*:*:*:*:*:* * cpe:2.3:a:hitachienergy:lumada_apm:6.4.0.0:*:*:*:*:*:*:*

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

This is an authorization bypass vulnerability in Lumada APM where the 'Limited Engineer' role incorrectly grants access to embedded Power BI reports and allows manipulation of asset issue comments that should be restricted. The flaw is in the access control implementation for the User Asset Group feature, enabling users with Limited Engineer privileges to access unauthorized resources.

MitigationApply vendor patch when available; in the interim, audit Limited Engineer role assignments, restrict access to sensitive Power BI reports, and monitor for unauthorized access or comment manipulation attempts.

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
Lumada Asset Performance ManagementApplication
Affected:>= 6.0.0.0, < 6.4.0.1

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

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

  1. Identify Lumada APM version
    Check the installed version of Hitachienergy Lumada Asset Performance Management. This is typically found in the product's About section, system information page, or version file within the installation directory. Compare against the affected range: >= 6.0.0.0 and < 6.4.0.1.
    Affected if Installed version falls within >= 6.0.0.0 and < 6.4.0.1
  2. Audit Limited Engineer role assignments
    Access the Lumada APM administrative console or user management interface. Review all users assigned the 'Limited Engineer' role. Export or document the list of users with this role.
    Affected if Any users are assigned the Limited Engineer role
  3. Verify Power BI integration status
    Check whether embedded Power BI reports are configured or enabled in the Lumada APM environment. This is typically found in the integration settings, reporting configuration, or dashboard settings within the product.
    Affected if Power BI reports are embedded or configured in the environment
  4. Inspect User Asset Group configuration
    Examine the User Asset Group feature settings in the access control or user management configuration. Verify how asset groups are assigned to Limited Engineer role users and whether proper filtering is applied.
    Affected if User Asset Group feature is enabled and accessible to Limited Engineer users
  5. Review asset issue comment access
    Test or review whether users with Limited Engineer role can access and manipulate asset issue comments. Check the access control permissions associated with comment creation, modification, or deletion for assets outside their assigned groups.
    Affected if Limited Engineer users can view or modify asset issue comments for resources outside their authorized scope

Environment is affected if running Lumada APM version 6.0.0.0 through 6.4.0.0 with Limited Engineer role assignments and Power BI integration enabled.

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.

dbcve · scoped
Upgrade available Upgrade to 6.4.0.1 or later
Fixed in 6.4.0.1
Interim mitigation

Apply vendor patch when available; in the interim, audit Limited Engineer role assignments, restrict access to sensitive Power BI reports, and monitor for unauthorized access or comment manipulation attempts.

Recommended fix Moderate confidence

Lumada APM version 6.4.0.1 or later

  1. Verify current Lumada APM version by checking the application's 'About' section or system information panel
  2. Schedule a maintenance window for the upgrade process
  3. Create a full backup of the current Lumada APM installation including database and configuration files
  4. Download Lumada APM version 6.4.0.1 or later from the official Hitachi Energy support portal (search.abb.com)
  5. Follow the standard upgrade procedure documented in the Lumada APM installation guide for your deployment type (on-premises)
  6. After upgrade, verify that the 'Limited Engineer' role no longer has access to Power BI reports feature by attempting to access reports with a Limited Engineer account
  7. Test that asset issue comments cannot be manipulated by Limited Engineer role users
  8. Confirm all users have appropriate roles and permissions after upgrade
Caveat Review release notes for version 6.4.0.1 for any configuration or feature changes that may affect existing workflows; standard upgrade precautions apply

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Lumada Asset Performance Management Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-2155 — 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-2022-2155 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