CVE-2022-29832
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 in Memory vulnerability in Mitsubishi Electric Corporation GX Works3 versions 1.015R and later, GX Works2 all versions and GX Developer versions 8.40S and later allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated users could obtain information about the project file for MELSEC safety CPU modules or project file for MELSEC Q/FX/L series with security setting.
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 in Mitsubishi's engineering software (GX Works3, GX Works2, GX Developer) stores sensitive information such as project file passwords and security settings in cleartext in memory. An unauthenticated remote attacker can exploit this to read sensitive data from memory, potentially gaining access to MELSEC safety CPU modules and Q/FX/L series PLC project files with security settings enabled.
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 Mitsubishi engineering softwareCheck installed programs for GX Works3, GX Works2, or GX Developer on the engineering workstationAffected if Any of these three products are installed
-
Determine GX Works3 versionOpen GX Works3, go to Help > Version Information, or check the program's file properties to find the exact version numberAffected if Version is >= 1.015r and <= 1.086q, or >= 1.087r
-
Check for GX Works2 or GX Developer installationsVerify if GX Works2 or GX Developer is installed, as these versions are also affected regardless of specific version numbersAffected if Either GX Works2 or GX Developer is installed
-
Identify if project files with security settings existLocate any .gxw3, .gxw2, or .gpx project files on the workstation that were opened with security settings (passwords, security keys) enabledAffected if Project files with security settings have been opened in the affected software
-
Assess network exposure of engineering workstationReview network access controls and firewall rules to determine if the workstation with the affected software is accessible from unauthorized network segmentsAffected if The workstation is accessible from network segments beyond the trusted engineering zone
The environment is affected if any version of GX Works3 within the specified ranges, or any version of GX Works2/GX Developer, has been used to handle project files with security settings, and the workstation is network-accessible to untrusted attackers.
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 dataApply vendor patches when released. In the interim, restrict network access to engineering workstations, implement strict access controls, and monitor for unauthorized access attempts to mitigate exposure of cleartext sensitive data in memory.
- Consultation4.0 h
- Testing6.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 $3,872.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29832 — 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-29832 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