dbcve.org
Replication ManagerApplication · Hitachi

CVE-2022-4146

CRITICAL · 9.8 CVSS v3.1 Published 2023-07-18
Fix available
A fix is available. Upgrade to 8.8.5-02 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Expression Language Injection vulnerability in Hitachi Replication Manager on Windows, Linux, Solaris allows Code Injection.This issue affects Hitachi Replication Manager: before 8.8.5-02.

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 confidence

An Expression Language Injection vulnerability in Hitachi Replication Manager allows attackers to inject and execute arbitrary code by crafting malicious EL expressions. The vulnerability affects versions prior to 8.8.5-02 across Windows, Linux, and Solaris platforms.

MitigationUpgrade to Hitachi Replication Manager version 8.8.5-02 or later to remediate this critical vulnerability.

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
Replication ManagerApplication
Affected:< 8.8.5-02

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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. Check installed Hitachi Replication Manager version
    Locate the Hitachi Replication Manager installation directory and find the version information file or use the product's version command. Common locations include /opt/hitachi/replicationmanager or C:\Program Files\Hitachi\ReplicationManager on Windows. Look for a version file, About dialog, or use the product's CLI if available.
    Affected if The installed version is any version prior to 8.8.5-02 (for example, 8.8.0, 8.7.x, or earlier)
  2. Identify if web interface or API is exposed
    Determine whether the Hitachi Replication Manager web console or REST API is accessible on the network. Check for listening ports typically used by the product (commonly 8080, 8443, or similar). Verify if the service is reachable from external or untrusted networks.
    Affected if The web interface or API is exposed and the installed version is below 8.8.5-02
  3. Check for unauthenticated or low-privilege access paths
    Review access controls and authentication settings for the Hitachi Replication Manager management interface. Determine if there are endpoints or functions that process user-supplied input without proper sanitization, particularly in areas where Expression Language evaluation might occur.
    Affected if Unauthenticated users or low-privilege accounts can submit input to the affected components and the version is below 8.8.5-02

The environment is affected if Hitachi Replication Manager is installed with a version lower than 8.8.5-02 and the management interface accepts user input that could trigger Expression Language evaluation.

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 8.8.5-02 or later
Fixed in 8.8.5-02
Interim mitigation

Upgrade to Hitachi Replication Manager version 8.8.5-02 or later to remediate this critical vulnerability.

Recommended fix High confidence

8.8.5-02

  1. Identify the current version of Hitachi Replication Manager installed in the environment
  2. Download Hitachi Replication Manager version 8.8.5-02 or later from the official Hitachi support portal at www.hitachi.com
  3. Plan and schedule a maintenance window to minimize business impact
  4. Back up all critical data and configuration files for the Replication Manager installation
  5. Stop the Hitachi Replication Manager services before performing the upgrade
  6. Install version 8.8.5-02 following the vendor's upgrade documentation
  7. Verify the installation completed successfully and services start without errors
  8. Validate that the upgrade resolved the Expression Language Injection vulnerability

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

Fix this in Replication Manager Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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