# CVE-2023-1424: Denial-of-Service and Remote Code Execution Vulnerability in MELSEC Series CPU module

> Remote unauthenticated attackers can cause denial of service or execute malicious code on Mitsubishi MELSEC CPU modules via crafted packets.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 May 2023
- **Updated:** 5 Mar 2025
- **Also known as:** GHSA-jrmr-8594-crxx

## What is CVE-2023-1424?

CVE-2023-1424 is a critical memory corruption vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5U-32MR/DS, published on 24 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series CPU modules and MELSEC iQ-R Series CPU modules allows a remote unauthenticated attacker to cause a denial of service (DoS) condition or execute malicious code on a target product by sending specially crafted packets. A system reset of the product is required for recovery from a denial of service (DoS) condition and malicious code execution.

Weakness: CWE-120 (Buffer Copy without Checking Size of Input)

## Which versions are affected by CVE-2023-1424?

It affects 39 products.


Products: Mitsubishielectric Melsec Iq-Fx5u-32mr\/Ds Firmware, Mitsubishielectric Melsec Iq-Fx5u-32mr\/Dss Firmware, Mitsubishielectric Melsec Iq-Fx5u-32mr\/Es Firmware, Mitsubishielectric Melsec Iq-Fx5u-32mr\/Ess Firmware, Mitsubishielectric Melsec Iq-Fx5u-32mt\/Ds Firmware, Mitsubishielectric Melsec Iq-Fx5u-32mt\/Dss Firmware, Mitsubishielectric Melsec Iq-Fx5u-32mt\/Es Firmware, Mitsubishielectric Melsec Iq-Fx5u-32mt\/Ess Firmware, Mitsubishielectric Melsec Iq-Fx5u-64mr\/Ds Firmware, Mitsubishielectric Melsec Iq-Fx5u-64mr\/Dss Firmware, Mitsubishielectric Melsec Iq-Fx5u-64mr\/Es Firmware, Mitsubishielectric Melsec Iq-Fx5u-64mr\/Ess Firmware, Mitsubishielectric Melsec Iq-Fx5u-64mt\/Ds Firmware, Mitsubishielectric Melsec Iq-Fx5u-64mt\/Dss Firmware, Mitsubishielectric Melsec Iq-Fx5u-64mt\/Es Firmware, Mitsubishielectric Melsec Iq-Fx5u-64mt\/Ess Firmware, Mitsubishielectric Melsec Iq-Fx5u-80mr\/Ds Firmware, Mitsubishielectric Melsec Iq-Fx5u-80mr\/Dss Firmware, Mitsubishielectric Melsec Iq-Fx5u-80mr\/Es Firmware, Mitsubishielectric Melsec Iq-Fx5u-80mr\/Ess Firmware and 19 more.

## How do I fix CVE-2023-1424?

No fix has been published for CVE-2023-1424 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-1424 being exploited?

There is no known exploitation of CVE-2023-1424 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-1424 and fix it if it is affected.

What it is: CVE-2023-1424 is a critical memory corruption vulnerability in Mitsubishi Electric Corporation MELSEC iQ-F Series FX5U-32MR/DS, published on 24 May 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-1424 in the wild and no public exploit code.

Affected product: Mitsubishi Electric Corporation MELSEC iQ-F Series FX5U-32MR/DS. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-1424/ (Markdown: https://insights.sbomify.com/CVE-2023-1424/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-1424
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-1424
- OSV: https://osv.dev/vulnerability/CVE-2023-1424

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-1424/
Summaries are generated and may contain mistakes; the official description above is the record.