Skip to main content
Mallory
HighVulnerability

CVE-2021-20613: DoS via Improper Initialization in Mitsubishi MELSEC-F FX3U-ENET Series

Published Jan 14, 2022 · Updated 1 month ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS3.8%90th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Mitsubishi Electric Corporation
IdentifiersCVE-2021-20613CWE-665 · Improper Initialization

An improper initialization vulnerability exists in the MELSEC-F series FX3U-ENET, FX3U-ENET-L, and FX3U-ENET-P502 firmware versions 1.16 and prior. A remote, unauthenticated attacker can exploit this by sending specially crafted packets to the device, causing a denial-of-service (DoS) in the communication function. The PLC's control logic is not affected, but a system reset is required to restore communication functionality.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a remote attacker to disrupt the communication function of the affected MELSEC-F series modules, resulting in a denial-of-service condition. The PLC's control operations remain unaffected, but the communication module becomes unresponsive until a manual reset is performed.

Mitigation

If you can’t patch tonight, do this now.

Restrict network access to the affected devices, segment control networks, and use firewalls or VPNs to limit exposure to untrusted networks. Monitor network traffic for suspicious activity targeting the communication modules.

Remediation

Patch, then assume compromise.

Update the FX3U-ENET, FX3U-ENET-L, and FX3U-ENET-P502 firmware to a version later than 1.16 that addresses the improper initialization vulnerability.

Public exploits

Exploits

No public exploits tracked yet. Mallory keeps watching.

View more in app →
No public exploit code observed for this vulnerability. Mallory keeps watching.
Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Mitsubishi Electric CorporationFx3u-Enet Firmwareoperating_system
Mitsubishi Electric CorporationFx3u-Enet-L Firmwareoperating_system
Mitsubishi Electric CorporationFx3u-Enet-P502 Firmwareoperating_system
FAQ

Frequently asked questions

Is CVE-2021-20613 exploited in the wild?
As of Oct 16, 2026, Mallory has no reports of CVE-2021-20613 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2021-20613?
As of Oct 16, 2026, Mallory has found no public exploit for CVE-2021-20613.
Is there a patch for CVE-2021-20613?
Update the FX3U-ENET, FX3U-ENET-L, and FX3U-ENET-P502 firmware to a version later than 1.16 that addresses the improper initialization vulnerability.
What products are affected by CVE-2021-20613?
Mitsubishi Electric Corporation Fx3u-Enet-P502 Firmware, Mitsubishi Electric Corporation Fx3u-Enet Firmware, and Mitsubishi Electric Corporation Fx3u-Enet-L Firmware.
How severe is CVE-2021-20613?
CVE-2021-20613 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 3.8% (90th percentile) as of Oct 16, 2026.
Activity feed

Recent activity

1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activityCommunity discussion across Reddit, Mastodon, and other social sources.