CVE-2022-29830
No exploitation reported by the sources we read.
- Published2022-11-25
- WeaknessCWE-321 · CWE-798
Am I affected?
Debian, Ubuntu or Red Hat sometimes backport a fix without changing the upstream version number: such a version reads « to verify », never « affected ».With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.
Description
Use of Hard-coded Cryptographic Key vulnerability in Mitsubishi Electric GX Works3 versions from 1.000A to 1.095Z, and Motion Control Setting(GX Works3 related software) versions from 1.000A to 1.065T allows a remote unauthenticated attacker to disclose or tamper with sensitive information. As a result, unauthenticated attackers may obtain information about project files illegally.
Timeline
dates in UTC- 2022-11-2500:15CVE publishedNVD
Observed activity
isMalicious corpus · updated 2026-10-23 21:37 UTCBlock these indicators
- Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2022-29830?format=txt
- CSV export: https://api.ismalicious.com/edl/cve/CVE-2022-29830?format=csv
- TAXII collection of exploited CVEs
- The EDL and CSV take an API key on the Pro plan.
Versions per branch
NVD| Branch | Affected | Fixed in | Source |
|---|---|---|---|
| 1.x | ≥ 1.000a, ≤ 1.011m | no fix published | NVD |
| 1.x | ≥ 1.015r, ≤ 1.086q | no fix published | NVD |
| 1.87+ | ≥ 1.087r | no fix published | NVD |
as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.
Distribution builds and vendor advisories
Packages from OSV.dev and products from the vendors' CSAF advisories.
version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.
Vendor advisories
Mitsubishi Electric FA Engineering Software (Update C)
Mitsubishi Electric GX Works3: >=1.000A|<1.011M · Mitsubishi Electric GX Works3: >=1.015R|<1.087R · Mitsubishi Electric GX Works3: 1.090U · +4 more
Fix
- Vendor fix CISA ICSA-22-333-05 · 4 productsGX Works3:
- Vendor fix CISA ICSA-22-333-05 · 4 productsCVE-2022-29830: Download fixed Ver. 1.070Y or later and update the software. Set security version for project to "2". Refer "Motion Control Setting Function Help" – "12.5. Preventing Illegal Access to/Falsification of Data (Security Version)" for details. Apply the countermeasure for CVE-2022-29830…
- Mitigation from the vendor CISA ICSA-22-333-05 · 7 productsMitsubishi Electric released and recommends users update to the latest version:
- Mitigation from the vendor CISA ICSA-22-333-05 · 7 productsCVE-2022-25164, CVE-2022-29830, and CVE-2022-29831: Download fixed Ver. 1.096A or later. Then set security version for project to "2".
- Mitigation from the vendor CISA ICSA-22-333-05 · 7 productsGT Designer3 Version1 (GOT2000):
- Mitigation from the vendor CISA ICSA-22-333-05 · 7 productsMotion Control Setting:
Advisories and patches
- www.mitsubishielectric.comMitigation · Vendor Advisory
Detection
- Nuclei template
- none so far ProjectDiscovery
- Exploit-DB
- no entry Exploit-DB
- Proof-of-concept repositories
- none listed PoC-in-GitHub
Sources
Technical details
- CVSS v3 Vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- Published
- 2022-11-25
- Last Modified
- 2026-06-17
- NVD status
- Modified
Frequently asked questions
What is CVE-2022-29830?
Is CVE-2022-29830 actively exploited?
What is the CVSS score for CVE-2022-29830?
Hear about the next vulnerability in your software
Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».
No credit card required · No monthly cap on website lookups · 250 API requests/month
Go further
- Following what attackers exploit right now? The CISA KEV additions of the month, with their patch deadlines.
- Running this software? Vulnerability monitoring alerts you to new vulnerabilities in your products.
Related vulnerabilities
Same product first, then the same vendor advisory and the same publication week.