EZSocket: Missing Authentication for Critical Functionality
CVE-2023-6942 is a high-severity missing authentication for critical functionality vulnerability in EZSocket from Mitsubishi Electric, with a CVSS 3.1 base score of 7.5 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected EZSocket versions: 3.0 to 5.92. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 0.95% chance of exploitation within 30 days, higher than 62% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Check which version of EZSocket you run against the affected versions below, and install the vendor's latest release.
- Read the advisory on mitsubishielectric.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Mitsubishi Electric | EZSocket | 3.0 to 5.92 | Not stated |
| Mitsubishi Electric | GT Designer3 Version1(GOT1000) | 1.325P and prior | Not stated |
| Mitsubishi Electric | GT Designer3 Version1(GOT2000) | 1.320J and prior | Not stated |
| Mitsubishi Electric | GX Works2 | 1.11M to 1.626C | Not stated |
| Mitsubishi Electric | GX Works3 | 1.106L and prior | Not stated |
| Mitsubishi Electric | MELSOFT Navigator | 1.04E to 2.102G | Not stated |
| Mitsubishi Electric | MT Works2 | 1.190Y and prior | Not stated |
| Mitsubishi Electric | MX Component | 4.00A to 5.007H | Not stated |
| Mitsubishi Electric | MX OPC Server DA/UA | all versions | Not stated |
| Mitsubishi Electric | Fr Configurator2 | Not specified in the record | Not stated |
| Mitsubishi Electric | Got1000 | Not specified in the record | Not stated |
| Mitsubishi Electric | Got2000 | Not specified in the record | Not stated |
| Mitsubishi Electric | Mc Works64 | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- NoneNo data is disclosed.
- Integrity
- HighData or code can be modified at will.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 7.5 | High | CNA (yd.MitsubishiElectric.co.jp) |
| CVSS 3.1 | 7.5 | High | NVD |
Official description
Missing Authentication for Critical Function vulnerability in Mitsubishi Electric Corporation EZSocket versions 3.0 to 5.92, GT Designer3 Version1(GOT1000) versions 1.325P and prior, GT Designer3 Version1(GOT2000) versions 1.320J and prior, GX Works2 versions 1.11M to 1.626C, GX Works3 versions 1.106L and prior, MELSOFT Navigator versions 1.04E to 2.102G, MT Works2 versions 1.190Y and prior, MX Component versions 4.00A to 5.007H and MX OPC Server DA/UA all versions allows a remote unauthenticated attacker to bypass authentication by sending specially crafted packets and connect to the products illegally.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Missing Authentication for Critical Functionality
The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
How developers prevent this class of flaw
- For any security checks that are performed on the client side, ensure that these checks are duplicated on the server side, in order to avoid CWE-602. Attackers can bypass the client-side checks by modifying values after the checks have been performed, or by changing the client to remove the client-side checks entirely. Then, these modified values would be submitted to the server.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, consider using libraries with authentication capabilities such as OpenSSL or the ESAPI Authenticator.
- When storing data in the cloud (e.g., S3 buckets, Azure blobs, Google Cloud Storage, etc.), use the provider's controls to require strong authentication for users who should be allowed to access the data.
More Missing Authentication for Critical Functionality vulnerabilities (CWE-306)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- jvn.jp/vu/JVNVU95103362Third Party Advisory
- cisa.gov/news-events/ics-advisories/icsa-24-030-02Third Party Advisory, US Government Resource
Other vulnerabilities in EZSocket
- 7.8 High severity
- 9.8 Critical severity
- 7.8 High severity
Recent Missing Authentication for Critical Functionality vulnerabilities
- 9.8 Critical severity
- 9.1 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
- 7.5 High severity
- 8.0 High severity
Spotted an error? Tell us.