CVE-2022-2513
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 · uneditedA 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.
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 confidenceIn Hitachi Energy's PCM600 product, the IED Connectivity Package (ConnPack) stores IED device credentials in cleartext within the PCM600 database and log files. An attacker with access to exported backup files or administrator access to the PCM600 host can read these plaintext credentials and use them to make unauthorized modifications to IEDs, load incorrect configurations, reboot devices, or cause denial-of-service.
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= 1.3.0= 2.1.2= 2.2.2= 2.3.0= 2.4.1= 3.0.2= 3.1.2= 3.2.6= 3.3.0= 3.4.1= 1.3.0= 1.3.1<= 2.11= 1.1.0= 1.1.1= 1.1.2= 1.2.0= 1.3.0= 1.0.0= 1.1.0= 1.2.0CVSS 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
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify PCM600 installation and versionLocate the PCM600 installation directory and check the product version information, typically found in the application About or Help menu, or in installed program files metadataAffected if PCM600 version is 2.11 or lower, or the exact version matches any of the listed affected connectivity package versions
-
Identify installed Connectivity Packages (ConnPacks)In PCM600, navigate to the Package Manager or Connectivity Package management section to list all installed IED Connectivity Packages and their versionsAffected if Any of these packages are installed: 650connectivitypackage (1.3.0, 2.1.2, 2.2.2, 2.3.0, 2.4.1), 670connectivitypackage (3.0.2, 3.1.2, 3.2.6, 3.3.0, 3.4.1), Gms600connectivitypackage (1.3.0, 1.3.1), Pwc600connectivitypackage (1.1.0-1.3.0), or Sam600ioconnectivitypackage (1.0.0-1.2.0)
-
Inspect PCM600 database files for cleartext credentialsExamine the PCM600 database files (typically .db, .sqlite, or proprietary format in the application data folder) for plaintext IED credentials, usernames, or passwords stored in fields related to IED device configurationAffected if Any IED device credentials (usernames, passwords, or authentication tokens) appear in cleartext rather than encrypted or hashed within the database
-
Search PCM600 log files for cleartext credentialsLocate and search PCM600 log files (typically in the application log directory or under the installation folder) for strings resembling credentials, password fields, or authentication data associated with IED devicesAffected if Log files contain plaintext IED credentials, passwords, or authentication tokens
-
Examine exported backup files for cleartext credentialsIf any PCM600 project backup files (.zip, .pcmbak, or other export formats) exist, extract and inspect them for plaintext credentials in database or configuration filesAffected if Exported backup files contain IED credentials stored in cleartext
A defender is affected if PCM600 version is 2.11 or lower, or any affected Connectivity Package version listed is installed, AND cleartext IED credentials can be found in the database, log files, or backup exports.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement encryption for IED credentials at rest in the database and log files, secure the backup export process, and apply any available vendor patches for PCM600 that address credential storage security.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-2513 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-2513 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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