CVE intelligence and bounded remediation

CVE-2022-2513 — Hitachienergy 650Connectivitypackage security vulnerability

High CVSS 7.1

A vulnerability exists in the Intelligent Electronic Device (IED) Connectivity Package (ConnPack) credential storage function in Hitachi Energy’s PCM600 product included in the versions listed below, where IEDs credentials are stored in a cleartext format in the PCM600 database and logs files. An attacker having get access to the exported backup file can exploit the vulnerability and obtain user credentials of the IEDs. Additionally, an attacker with administrator access to the PCM600 host machine can obtain other user credentials by analyzing database log files. The credentials may be used to perform unauthorized modifications such as loading incorrect configurations, reboot the IEDs or cause a denial-of-service on the IEDs.

Severity
High
CVSS
7.1 (3.1)
Published
2022-11-22
CISA KEV
Not currently listed
Ecosystem
software/application
Weaknesses
CWE-312

Affected products

  • hitachienergy / 650connectivitypackage / 1.3.0
  • hitachienergy / 650connectivitypackage / 2.1.2
  • hitachienergy / 650connectivitypackage / 2.2.2
  • hitachienergy / 650connectivitypackage / 2.3.0
  • hitachienergy / 650connectivitypackage / 2.4.1
  • hitachienergy / 670connectivitypackage / 3.0.2

Showing 6 representative product identities from 21 source matches. Confirm exact affected versions with the linked vendor and NVD evidence.

Matched remediation archetype

General vulnerability remediation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Confirm the affected component, deployment paths, reachable interfaces, and enabled features from inventories and configuration, without probing production destructively.
  • Compare the advisory's affected conditions with the repository lockfiles, build manifests, artifacts, and runtime inventory.
  • Identify data sensitivity, trust boundaries, and privilege level for every confirmed affected deployment.

Remediate safely

  • Apply a vendor-supported fix or remove the affected component or feature; record the selected change and its source in the repository.
  • Update direct and transitive dependency locks, generated artifacts, deployment manifests, and asset inventories together.
  • Add a regression test for the documented unsafe condition using inert inputs and preserve rollback instructions.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.