CVE-2022-29828
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 · uneditedUse of Hard-coded Cryptographic Key vulnerability in Mitsubishi Electric GX Works3 versions from 1.000A and later allows a remote unauthenticated attacker to disclose sensitive information. As a result, unauthenticated attackers may view programs and project file or execute programs illegally.
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 confidenceHard-coded cryptographic key vulnerability in Mitsubishi Electric GX Works3 allows remote unauthenticated attackers to decrypt sensitive project data, view programs and project files, and potentially execute programs illegally. The key is embedded in the software itself, enabling attackers to bypass authentication and access plaintext sensitive information.
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.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
- 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 installed GX Works3 versionOpen GX Works3 and navigate to the About or Version information section in the software menu, or check the program's properties in Windows Task Manager or Add/Remove ProgramsAffected if The displayed version falls within >= 1.000a to <= 1.011m, >= 1.015r to <= 1.086q, or >= 1.087r (versions 1.012-1.014 are NOT affected)
-
Verify affected version rangeCompare your installed version number against the affected ranges: 1.000a through 1.011m, 1.015r through 1.086q, and 1.087r and higherAffected if Your version matches any of the affected ranges listed above
-
Locate project filesSearch for .gxw or other project file extensions associated with GX Works3 on the system, typically found in user project directories or default installation pathsAffected if Unencrypted project files exist on the system containing sensitive automation logic or credentials
-
Check network exposureReview firewall rules and network configuration to determine if the GX Works3 software or associated ports/services are accessible from untrusted networksAffected if The system running GX Works3 or its project files is directly exposed to the internet or untrusted LAN segments
You are affected if GX Works3 is installed with a version matching the affected ranges AND sensitive project files exist on the system or are accessible over the network.
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 available, rotate any exposed credentials, review project files for unauthorized access, and restrict network exposure of affected systems.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-29828 — 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-29828 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