MITSUBISHI CNC M800V Series M800VW: Buffer Copy without Checking Size of Input
CVE-2023-3346 is a critical-severity buffer copy without checking size of input vulnerability in MITSUBISHI CNC M800V Series M800VW from Mitsubishi Electric, with a CVSS 3.1 base score of 9.8 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. Affected MITSUBISHI CNC M800V Series M800VW versions: System Number BND-2051W000 versions A8 and prior. The record does not name a fixed version, so check the vendor advisory. There is no confirmed exploitation so far. EPSS estimates a 2.1% chance of exploitation within 30 days, higher than 82% of scored CVEs.
Critical severity: a successful attack would have severe impact.
What to do
- Check which version of MITSUBISHI CNC M800V Series M800VW 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 | MITSUBISHI CNC M800V Series M800VW | System Number BND-2051W000 versions A8 and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M800V Series M800VS | System Number BND-2052W000 versions A8 and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M80V Series M80V | System Number BND-2053W000 versions A8 and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M80V Series M80VW | System Number BND-2054W000 versions A8 and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M800 Series M800W | System Number BND-2005W000 versions FB and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M800 Series M800S | System Number BND-2006W000 versions FB and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M80 Series M80 | System Number BND-2007W000 versions FB and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M80 Series M80W | System Number BND-2008W000 versions FB and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC E80 Series E80 | System Number BND-2009W000 versions FB and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC C80 Series C80 | System Number BND-2036W000 versions BF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M700V Series M720VW | System Number BND-1015W000 versions LF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M700V Series M730VW | System Number BND-1015W000 versions LF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M700V Series M750VW | System Number BND-1015W002 versions LF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M700V Series M720VS | System Number BND-1012W000 versions LF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M700V Series M730VS | System Number BND-1012W000 versions LF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M700V Series M750VS | System Number BND-1012W002 versions LF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC M70V Series M70V | System Number BND-1018W000 versions LF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC E70 Series E70 | System Number BND-1022W000 versions LF and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC IoT Unit Remote Service Gateway Unit | System Number BND-2041W001 versions AD and prior | Not stated |
| Mitsubishi Electric | MITSUBISHI CNC IoT Unit Data Acquisition Unit | System Number BND-2041W002 all versions | Not stated |
| Mitsubishi Electric | C80 Firmware | Not specified in the record | Not stated |
| Mitsubishi Electric | E70 Firmware | Not specified in the record | Not stated |
| Mitsubishi Electric | E80 Firmware | Not specified in the record | Not stated |
| Mitsubishi Electric | M70v Firmware | Not specified in the record | Not stated |
| Mitsubishi Electric | M720vs Firmware | Not specified in the record | Not stated |
Version data comes from the organisation that assigned the CVE; 16 further products are omitted here. 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
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 9.8 | Critical | CNA (yd.MitsubishiElectric.co.jp) |
| CVSS 3.1 | 9.8 | Critical | NVD |
Official description
Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in MITSUBSHI CNC Series allows a remote unauthenticated attacker to cause Denial of Service (DoS) condition and execute arbitrary code on the product by sending specially crafted packets. In addition, system reset is required for recovery.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Buffer Copy without Checking Size of Input
The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
More Buffer Copy without Checking Size of Input vulnerabilities (CWE-120)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: yes, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Third-party and government advisories
- jvn.jp/vu/JVNVU90352157/index.htmlThird Party Advisory
- cisa.gov/news-events/ics-advisories/icsa-23-208-03Third Party Advisory, US Government Resource
Recent Buffer Copy without Checking Size of Input vulnerabilities
- 8.8 High severity
- 7.5 High severity
- 8.8 High severity
- 9.8 Critical severity
- 9.8 Critical severity
- 9.8 Critical severity
Spotted an error? Tell us.