CVE-2022-25164
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 · uneditedCleartext Storage of Sensitive Information vulnerability in Mitsubishi Electric GX Works3 versions from 1.000A to 1.095Z and Mitsubishi Electric MX OPC UA Module Configurator-R versions 1.08J and prior allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated attackers can gain unauthorized access to the MELSEC CPU module and the MELSEC OPC UA server module.
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 confidenceThis vulnerability involves cleartext (unencrypted) storage of sensitive information in Mitsubishi Electric GX Works3 and MX OPC UA Module Configurator-R. An unauthenticated remote attacker can exploit this to disclose stored credentials or sensitive data, enabling unauthorized access to MELSEC CPU modules and OPC UA servers.
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.000a, <= 1.011m>= 1.015r, <= 1.086q>= 1.087rall versionsCVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 GX Works3 installed versionUse system utilities or the program's 'About' dialog to determine the installed version of GX Works3. Compare the version number against the affected ranges: 1.000a through 1.011m, 1.015r through 1.086q, or 1.087r and later.Affected if The installed version falls within any of these ranges: 1.000a-1.011m, 1.015r-1.086q, or is 1.087r or higher.
-
Confirm MX OPC UA Module Configurator-R presenceDetermine if MX OPC UA Module Configurator-R is installed in the environment, regardless of version.Affected if MX OPC UA Module Configurator-R is present on the system.
-
Locate stored credential filesSearch project files, configuration directories, and data storage locations associated with GX Works3 and MX OPC UA Module Configurator-R for files that may contain stored credentials, keys, or authentication data.Affected if Credential-containing files exist in GX Works3 or MX OPC UA Module Configurator-R directories.
-
Inspect credential storage encryptionExamine stored credential files or configuration data to determine whether sensitive information such as passwords, keys, or authentication tokens is stored in encrypted form or in plaintext.Affected if Credentials or sensitive data are stored in cleartext (unencrypted) format.
The environment is affected if GX Works3 version is within the ranges 1.000a-1.011m, 1.015r-1.086q, or >=1.087r, or if MX OPC UA Module Configurator-R of any version is installed, and either product stores credentials in unencrypted form.
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 all stored sensitive data (credentials, keys, configuration secrets) using strong cryptographic algorithms. Rotate any exposed credentials and implement secure authentication mechanisms.
- Consultation8.0 h
- Implementation40.0 h
- Testing24.0 h
- Review / QA12.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $23,296.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-25164 — 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-25164 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