dbcve.org
Infrastructure Analytics AdvisorApplication · Hitachi

CVE-2022-41552

CRITICAL · 9.8 CVSS v3.1 Published 2022-11-01
Fix available
A fix is available. Upgrade to 10.9.0-00 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
Server-Side Request Forgery (SSRF) vulnerability in Hitachi Infrastructure Analytics Advisor on Linux (Data Center Analytics, Analytics probe components), Hitachi Ops Center Analyzer on Linux (Hitachi Ops Center Analyzer detail view, Hitachi Ops Center Analyzer probe components) allows Server Side Request Forgery. 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.0-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

Server-Side Request Forgery (SSRF) vulnerability in Hitachi Infrastructure Analytics Advisor and Hitachi Ops Center Analyzer allows attackers to make the server perform arbitrary requests to internal or external resources. This critical flaw (CVSS 9.8) affects the Data Center Analytics and Analytics probe components, potentially enabling internal network reconnaissance, cloud metadata access, and pivoting to internal services.

MitigationApply vendor-supplied patches: upgrade Hitachi Infrastructure Analytics Advisor to 4.4.1-00 or later, and Hitachi Ops Center Analyzer to 10.9.0-00 or later. Until patched, restrict network access and disable unnecessary outbound connections from affected systems.

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, <= 4.4.0-00
Ops Center AnalyzerApplication
Affected:>= 10.0.0-00, < 10.9.0-00
Ops Center ViewpointApplication
Affected:>= 10.8.0-00, < 10.9.0-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
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. Identify installed Hitachi product
    Locate the installed Hitachi software by checking installed applications or services. Look for 'Hitachi Infrastructure Analytics Advisor', 'Hitachi Ops Center Analyzer', or 'Hitachi Ops Center Viewpoint' in the system inventory or installed programs list.
    Affected if Any of these three products are installed on the system
  2. Determine installed version
    Check the version of the installed Hitachi product. This is typically found in the product's UI under 'About' or in the installation directory. For command-line access, consult product documentation for version lookup commands or check configuration files in the installation path.
    Affected if Version falls within the affected ranges: Infrastructure Analytics Advisor 2.0.0-00 to 4.4.0-00, Ops Center Analyzer 10.0.0-00 to below 10.9.0-00, or Ops Center Viewpoint 10.8.0-00 to below 10.9.0-00
  3. Verify Data Center Analytics or Analytics probe component is active
    Access the product admin interface and check if Data Center Analytics or Analytics probe components are enabled and configured. These are the specific components where the SSRF flaw exists.
    Affected if Either Data Center Analytics or Analytics probe component is enabled and running on an affected version
  4. Assess network exposure
    Review firewall rules and network configuration to determine if the affected product is accessible from untrusted networks. SSRF allows attackers to make the server perform arbitrary requests, so external accessibility increases risk.
    Affected if The product is reachable from external or untrusted networks without proper filtering

You are affected if any of these Hitachi products (Infrastructure Analytics Advisor, Ops Center Analyzer, or Ops Center Viewpoint) are installed with versions matching the affected ranges AND the Data Center Analytics or Analytics probe component is 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.

From vendor data
Upgrade available Upgrade to 10.9.0-00 or later
Fixed in 10.9.0-00
Interim mitigation

Apply vendor-supplied patches: upgrade Hitachi Infrastructure Analytics Advisor to 4.4.1-00 or later, and Hitachi Ops Center Analyzer to 10.9.0-00 or later. Until patched, restrict network access and disable unnecessary outbound connections from affected systems.

Fix this in Infrastructure Analytics Advisor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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