dbcve.org
Melsec Iq Fx5u 32mt\/es FirmwareOperating system · Mitsubishielectric

CVE-2022-25162

MEDIUM · 5.3 CVSS v3.1 Published 2022-05-18
Fix available
A fix is available. Upgrade to 1.270 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
Improper Input Validation vulnerability in Mitsubishi Electric MELSEC iQ-F series FX5U-xMy/z(x=32,64,80, y=T,R, z=ES,DS,ESS,DSS) with serial number 17X**** or later and versions prior to 1.270, Mitsubishi Electric Mitsubishi Electric MELSEC iQ-F series FX5U-xMy/z(x=32,64,80, y=T,R, z=ES,DS,ESS,DSS) with serial number 179**** and prior and versions prior to 1.073, MELSEC iQ-F series FX5UC-xMy/z(x=32,64,96, y=T,R, z=D,DSS) with serial number 17X**** or later and versions prior to 1.270, Mitsubishi Electric MELSEC iQ-F series FX5UC-xMy/z(x=32,64,96, y=T,R, z=D,DSS) with serial number 179**** and prior and versions prior to 1.073, Mitsubishi Electric MELSEC iQ-F series FX5UC-32MT/DS-TS versions prior to 1.270, Mitsubishi Electric MELSEC iQ-F series FX5UC-32MT/DSS-TS versions prior to 1.270, Mitsubishi Electric MELSEC iQ-F series FX5UC-32MR/DS-TS versions prior to 1.270, Mitsubishi Electric MELSEC iQ-F series FX5UJ-xMy/z(x=24,40,60, y=T,R, z=ES,ESS) versions prior to 1.030, Mitsubishi Electric MELSEC iQ-F series FX5UJ-xMy/ES-A(x=24,40,60, y=T,R) versions prior to 1.031 and Mitsubishi Electric MELSEC iQ-F series FX5S-xMy/z(x=30,40,60,80, y=T,R, z=ES,ESS) version 1.000 allows a remote unauthenticated attacker to cause a temporary DoS condition for the product's communication by sending specially crafted packets.

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 confidence

This is an improper input validation vulnerability in Mitsubishi Electric MELSEC iQ-F series PLCs (FX5U, FX5UC, FX5UJ, FX5S). A remote unauthenticated attacker can cause a temporary denial of service condition for the device's communication by sending specially crafted packets. The vulnerability affects specific models with certain serial numbers and firmware versions prior to the fixes.

MitigationApply the vendor-supplied firmware updates (v1.270 for FX5U/FX5UC, v1.030/1.031 for FX5UJ, v1.000 for FX5S). As a compensating control, implement network segmentation and firewall rules to limit exposure of affected devices to untrusted networks.

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
Melsec Iq Fx5u 32mt\/es FirmwareOperating system
Affected:< 1.270
Melsec Iq Fx5u 32mt\/ds FirmwareOperating system
Affected:< 1.270
Melsec Iq Fx5u 32mt\/ess FirmwareOperating system
Affected:< 1.270
Melsec Iq Fx5u 32mt\/dss FirmwareOperating system
Affected:< 1.270
Melsec Iq Fx5u 32mr\/es FirmwareOperating system
Affected:< 1.270
Melsec Iq Fx5u 32mr\/ds FirmwareOperating system
Affected:< 1.270
Melsec Iq Fx5u 32mr\/ess FirmwareOperating system
Affected:< 1.270
Melsec Iq Fx5u 32mr\/dss FirmwareOperating system
Affected:< 1.270

CVSS 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
None
Integrity
None
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the PLC model number
    Locate the model label on the physical PLC unit or check the system configuration in GX Works3 programming software under 'FX5U' or model information
    Affected if The model is not one of the FX5U variants (FX5UC, FX5UJ, FX5S have separate version requirements)
  2. Check the firmware version via GX Works3
    Connect to the PLC using GX Works3, go to 'Online' > 'Transfer Setup' and read the module firmware version from the CPU module information, or check via 'System Monitor' > 'Product Information'
    Affected if Firmware version is below 1.270 for the listed FX5U models (32MT/ES, 32MT/DS, 32MT/ESS, 32MT/DSS, 32MR/ES, 32MR/DS, 32MR/ESS, 32MR/DSS)
  3. Verify the CPU module serial number
    In GX Works3, access 'System Monitor' and view the CPU serial number information; the vulnerability may also be limited to specific serial number ranges per vendor advisory
    Affected if The device has specific serial numbers within the affected range as documented by Mitsubishi Electric advisory (REL-220001)
  4. Assess network exposure
    Review network firewall rules and segmentation to determine if the PLC Ethernet port (MELSEC connection, SLMP, or HTTP) is accessible from untrusted networks
    Affected if The PLC is directly accessible from outside the trusted network without firewall protection

The environment is affected if the PLC is a vulnerable FX5U model with firmware version below 1.270 and is network-accessible to untrusted attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.270 or later
Fixed in 1.270
Interim mitigation

Apply the vendor-supplied firmware updates (v1.270 for FX5U/FX5UC, v1.030/1.031 for FX5UJ, v1.000 for FX5S). As a compensating control, implement network segmentation and firewall rules to limit exposure of affected devices to untrusted networks.

Recommended fix High confidence

Firmware version 1.270 or later (FX5U/FX5UC), version 1.030/1.031 or later (FX5UJ), or latest available version (FX5S)

  1. Identify the exact model number and current firmware version of the MELSEC iQ-F series PLC (FX5U, FX5UC, FX5UJ, or FX5S)
  2. Download the firmware update from the official Mitsubishi Electric download page (www.mitsubishielectric.com) - ensure the firmware version is 1.270 or later for FX5U/FX5UC models, 1.030/1.031 or later for FX5UJ models, or the latest available version for FX5S models
  3. Use Mitsubishi GX Works3 software to connect to the PLC via USB or Ethernet
  4. Backup the current PLC program and parameters before performing the firmware update
  5. Transfer the firmware update to the PLC following the instructions in the Mitsubishi firmware update manual
  6. After the update completes, verify the firmware version has been successfully upgraded by checking the PLC diagnostics
  7. Restore the backed-up program and parameters if needed
  8. Test normal communication functionality to confirm the DoS vulnerability is remediated
Caveat Review Mitsubishi release notes for any parameter or configuration changes between your current version and the target version; some legacy settings may require adjustment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Melsec Iq Fx5u 32mt\/es Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25162 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-25162 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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