dbcve.org
Fx5uc FirmwareOperating system · Mitsubishielectric

CVE-2022-25158

CRITICAL · 9.1 CVSS v3.1 Published 2022-04-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
Cleartext Storage of Sensitive Information vulnerability in Mitsubishi Electric MELSEC iQ-F series FX5U(C) CPU all versions, Mitsubishi Electric MELSEC iQ-F series FX5UJ CPU all versions, Mitsubishi Electric MELSEC iQ-R series R00/01/02CPU all versions, Mitsubishi Electric MELSEC iQ-R series R04/08/16/32/120(EN)CPU all versions, Mitsubishi Electric MELSEC iQ-R series R08/16/32/120SFCPU all versions, Mitsubishi Electric MELSEC iQ-R series R08/16/32/120PCPU all versions, Mitsubishi Electric MELSEC iQ-R series R08/16/32/120PSFCPU all versions, Mitsubishi Electric MELSEC iQ-R series RJ71C24(-R2/R4) all versions, Mitsubishi Electric MELSEC iQ-R series RJ71EN71 all versions, Mitsubishi Electric MELSEC iQ-R series RJ71GF11-T2 all versions, Mitsubishi Electric MELSEC iQ-R series RJ71GP21(S)-SX all versions, Mitsubishi Electric MELSEC iQ-R series RJ72GF15-T2 all versions, Mitsubishi Electric MELSEC Q series Q03UDECPU all versions, Mitsubishi Electric MELSEC Q series Q04/06/10/13/20/26/50/100UDEHCPU all versions, Mitsubishi Electric MELSEC Q series Q03/04/06/13/26UDVCPU all versions, Mitsubishi Electric MELSEC Q series Q04/06/13/26UDPVCPU all versions, Mitsubishi Electric MELSEC Q series QJ71C24N(-R2/R4) all versions, Mitsubishi Electric MELSEC Q series QJ71E71-100 all versions, Mitsubishi Electric MELSEC L series L02/06/26CPU(-P) all versions, Mitsubishi Electric MELSEC L series L26CPU-(P)BT all versions, Mitsubishi Electric MELSEC L series LJ71C24(-R2) all versions, Mitsubishi Electric MELSEC L series LJ71E71-100 all versions and Mitsubishi Electric MELSEC L series LJ72GF15-T2 all versions allows a remote attacker to disclose or tamper with a file in which password hash is saved in cleartext.

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 vulnerability allows a remote attacker to access files containing password hashes stored in cleartext on affected Mitsubishi Electric MELSEC PLCs and communication modules. An attacker who gains access to these files can either read the plaintext-equivalent password hashes (enabling offline cracking) or tamper with them to gain unauthorized access to the device.

MitigationMitsubishi Electric has released firmware updates for affected devices; organizations should apply vendor patches, change all passwords that may have been stored on affected devices, and implement network segmentation to limit exposure to this and similar attacks.

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
Fx5uc FirmwareOperating system
Affected:all versions
Fx5uc 32mr\/ds Ts FirmwareOperating system
Affected:all versions
Fx5uc 32mt\/d FirmwareOperating system
Affected:all versions
Fx5uc 32mt\/dss FirmwareOperating system
Affected:all versions
Fx5uj 24mr\/es FirmwareOperating system
Affected:all versions
Fx5uj 24mt\/es FirmwareOperating system
Affected:all versions
Fx5uj 24mt\/ess FirmwareOperating system
Affected:all versions
Fx5uj 40mr\/es FirmwareOperating system
Affected:all versions

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
High
Integrity
High
Availability
None

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

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 device model
    Access the PLC configuration or use GX Works3 software to determine the exact model number (e.g., FX5UC, FX5UJ series)
    Affected if The device is one of the following: FX5UC, FX5UC-32MR/DS, FX5UC-32MT/D, FX5UC-32MT/DSS, FX5UJ-24MR/ES, FX5UJ-24MT/ES, FX5UJ-24MT/ESS, or FX5UJ-40MR/ES
  2. Confirm the device has password protection configured
    Check the PLC project settings in GX Works3 or via the device web interface for any configured passwords (user passwords, program protection passwords, or security settings)
    Affected if Any password or security protection is configured on the device
  3. Verify password hash storage accessibility
    Attempt to access or backup the PLC project file via GX Works3 or the SD card slot if present; examine whether the backup or project file contains readable password-related data
    Affected if The device stores password hashes in a file that can be extracted or read without decryption
  4. Check firmware version
    Use GX Works3 or the device diagnostics to retrieve the firmware version
    Affected if The firmware version is any version (all versions of affected models are vulnerable)

If the device is an affected MELSEC model (FX5UC or FX5UJ series) and has any password protection configured, the password hashes may be accessible in cleartext and the environment is affected by this CVE.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Mitsubishi Electric has released firmware updates for affected devices; organizations should apply vendor patches, change all passwords that may have been stored on affected devices, and implement network segmentation to limit exposure to this and similar attacks.

Fix this in Fx5uc Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA8.0 h
52.0 hours of engineering $9,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-25158 — 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-25158 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