dbcve.org
Infrastructure Analytics AdvisorApplication · Hitachi

CVE-2022-4895

HIGH · 8.1 CVSS v3.1 Published 2023-02-28
Fix available
A fix is available. Upgrade to 10.9.1-00 or later.
See remediation →
90/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
Improper Certificate Validation vulnerability in Hitachi Infrastructure Analytics Advisor on Linux (Analytics probe component), Hitachi Ops Center Analyzer on Linux (Analyzer probe component) allows Man in the Middle Attack.This issue affects Hitachi Infrastructure Analytics Advisor: from 2.0.0-00 through 4.4.0-00; Hitachi Ops Center Analyzer: from 10.0.0-00 before 10.9.1-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 · high confidence

Improper certificate validation in Hitachi Infrastructure Analytics Advisor and Ops Center Analyzer probe components on Linux allows man-in-the-middle attackers to intercept communications by presenting invalid or fraudulent SSL/TLS certificates, potentially exposing sensitive analytics data.

MitigationUpdate to Hitachi Infrastructure Analytics Advisor 4.4.0-01 or later, or Ops Center Analyzer 10.9.1-00 or later. If patching is delayed, restrict network access to trusted paths and monitor for anomalous SSL/TLS behavior.

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
Infrastructure Analytics AdvisorApplication
Affected:>= 2.0.0-00, < 10.9.1-00
Ops Center AnalyzerApplication
Affected:>= 10.0.0-00, < 10.9.1-00

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

CVSS:3.1/AV:N/AC:H/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. Identify installed Hitachi product
    Run 'rpm -qa | grep -i Hitachi' or check /opt/hitachi directory for product presence. Look for packages containing 'Infrastructure Analytics Advisor' or 'Ops Center Analyzer' in the package name or product directory.
    Affected if Neither Hitachi Infrastructure Analytics Advisor nor Ops Center Analyzer is installed - not affected.
  2. Determine Infrastructure Analytics Advisor version
    If HIAA is present, run 'rpm -qi Hitachifile' or check version file in the installation directory, typically /opt/hitachi/aiad/ or similar product directories. Look for version string in format like X.X.X-XX.
    Affected if Version is 2.0.0-00 or higher but lower than 10.9.1-00 - potentially affected.
  3. Determine Ops Center Analyzer version
    If OCA is present, run 'rpm -qi' on the analyzer probe package or check version in the installation directory, typically under /opt/hitachi/oc/. Look for version string in format X.X.X-XX.
    Affected if Version is 10.0.0-00 or higher but lower than 10.9.1-00 - potentially affected.
  4. Verify probe components are configured
    Check if the analyzer probe service is running and network listeners are active. Use 'ps aux | grep probe' or check configuration files in etc/ for enabled probe endpoints.
    Affected if Probe components are enabled and communicating over network - affected if version is in vulnerable range.

User is affected if Hitachi Infrastructure Analytics Advisor (version 2.0.0-00 to < 10.9.1-00) or Ops Center Analyzer (version 10.0.0-00 to < 10.9.1-00) is installed with the probe components enabled and handling network traffic.

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 10.9.1-00 or later
Fixed in 10.9.1-00
Interim mitigation

Update to Hitachi Infrastructure Analytics Advisor 4.4.0-01 or later, or Ops Center Analyzer 10.9.1-00 or later. If patching is delayed, restrict network access to trusted paths and monitor for anomalous SSL/TLS behavior.

Recommended fix High confidence

10.9.1-00

  1. Upgrade Hitachi Infrastructure Analytics Advisor to version 10.9.1-00 or later
  2. Upgrade Hitachi Ops Center Analyzer to version 10.9.1-00 or later
  3. After upgrade, verify that SSL/TLS certificate validation is functioning properly for probe components

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

Fix this in Infrastructure Analytics Advisor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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