CVE-2022-29833
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 · uneditedInsufficiently Protected Credentials vulnerability in Mitsubishi Electric Corporation GX Works3 versions 1.015R and later allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated users could access to MELSEC safety CPU modules illgally.
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 · moderate confidenceInsufficiently Protected Credentials vulnerability in GX Works3 versions 1.015R and later allows remote unauthenticated attackers to intercept or access sensitive credentials, enabling illegal access to MELSEC safety CPU modules.
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.015r, <= 1.086q>= 1.087rCVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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 installed GX Works3 versionNavigate to the GX Works3 installation directory (typically C:\Program Files\Mitsubishi Electric\GX Works3) and locate the GXWorks3.exe file. Right-click the executable, select Properties, and check the Details tab for the Product Version or File Version.Affected if The version displayed is 1.015R or any later version (1.015R through 1.086Q, or 1.087R and above)
-
Locate GX Works3 project and credential filesCheck the user documents folder or custom project storage location for .gxw or related project files. Also check the GX Works3 installation directory for configuration folders that may contain saved credentials or connection settings.Affected if Credentials, connection strings, or CPU module authentication data are stored in plaintext or with weak encryption in configuration or project files
-
Verify network exposure of MELSEC safety CPU modulesIf MELSEC safety CPU modules are configured in GX Works3 projects, check the network configuration settings (particularly the Ethernet or CC-Link IE settings) to determine if these modules are accessible over network interfaces that could be reached by unauthenticated attackers.Affected if Safety CPU modules are configured with network connections accessible from untrusted networks without additional access controls
A user is affected if GX Works3 version 1.015R or later is installed and the environment involves MELSEC safety CPU modules with network-accessible credentials or connection configurations.
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 dataUpdate GX Works3 to a patched version that properly encrypts/protects credentials and implement network segmentation to limit exposure of industrial control systems to untrusted networks.
- Consultation6.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,144.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29833 — 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-29833 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