CVE-2023-0525
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 · uneditedWeak Encoding for Password vulnerability in Mitsubishi Electric Corporation GOT2000 Series GT27 model versions 01.49.000 and prior, GT25 model versions 01.49.000 and prior, GT23 model versions 01.49.000 and prior, GT21 model versions 01.49.000 and prior, GOT SIMPLE Series GS25 model versions 01.49.000 and prior, GS21 model versions 01.49.000 and prior, GT Designer3 Version1 (GOT2000) versions 1.295H and prior and GT SoftGOT2000 versions 1.295H and prior allows a remote unauthenticated attacker to obtain plaintext passwords by sniffing packets containing encrypted passwords and decrypting the encrypted passwords, in the case of transferring data with GT Designer3 Version1(GOT2000) and GOT2000 Series or GOT SIMPLE Series with the Data Transfer Security function enabled, or in the case of transferring data by the SoftGOT-GOT link function with GT SoftGOT2000 and GOT2000 series with the Data Transfer Security function enabled.
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 confidenceThe vulnerability exists in the weak encoding mechanism used for password protection during data transfer. When the Data Transfer Security function is enabled on GOT2000 Series HMIs or GT Designer3/SoftGOT2000, passwords are encoded (not properly encrypted) and transmitted in easily reversible form. A remote attacker can sniff network traffic containing these encoded passwords and decrypt them to obtain plaintext credentials.
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.300n< 1.300n< 01.50.000< 01.50.000< 01.50.000< 01.50.000< 01.50.000< 01.50.000CVSS 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.
-
Check GT Designer3 or SoftGOT2000 software versionOpen GT Designer3 or SoftGOT2000, navigate to Help > About or check the software's version information in the application menuAffected if Version is less than 1.300N
-
Check GOT2000 HMI firmware versionAccess the HMI device via GT Designer3 or directly on the touchscreen: go to System Settings > Maintenance > Firmware Version, or check the sticker on the deviceAffected if Firmware version is less than 01.50.000 for GT27/GT25/GT23/GT21/GS25/GS21
-
Verify Data Transfer Security is enabledIn GT Designer3, open the project and go to Common Settings > Transfer Setup > Data Transfer Security; check if the option is enabledAffected if Data Transfer Security function is turned ON
-
Assess network accessibilityReview network topology and firewall rules to determine if the HMI and transfer traffic are exposed to untrusted networksAffected if HMI is reachable from networks where an attacker could sniff network traffic
You are affected if your GT Designer3/SoftGOT2000 version is below 1.300N OR your HMI firmware is below 01.50.000, AND Data Transfer Security is enabled, AND the device is on an accessible 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.
dbcve · scoped01.50.0001.300n
Update Mitsubishi Electric GOT2000/GOT SIMPLE Series firmware to versions beyond 01.49.000 and GT Designer3/SoftGOT2000 to versions beyond 01.295H. Alternatively, disable the Data Transfer Security function if operationally feasible and use network segmentation to limit exposure to untrusted networks.
GT27/GT25/GT23/GT21/GS25/GS21 firmware: 01.50.000 | GT Designer3: 1.300n | GT SoftGOT2000: 1.300n
- 1. Identify all affected Mitsubishi Electric products in your environment (GT27, GT25, GT23, GT21, GS25, GS21, GT Designer3, GT SoftGOT2000)
- 2. For GOT2000 series and GOT SIMPLE series devices (GT27, GT25, GT23, GT21, GS25, GS21): Update firmware to version 01.50.000 or later
- 3. For GT Designer3: Update to version 1.300n or later
- 4. For GT SoftGOT2000: Update to version 1.300n or later
- 5. After updating, verify the Data Transfer Security function is properly configured
- 6. Ensure network segmentation is in place to protect data-in-transit between engineering workstation and GOT devices
- 7. Consider implementing additional authentication mechanisms beyond the Data Transfer Security function
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-0525 — 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-2023-0525 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