dbcve.org
Fx5 Enet\/ip FirmwareOperating system · Mitsubishielectric

CVE-2023-2061

HIGH · 7.5 CVSS v3.1 Published 2023-06-02
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
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
Use of Hard-coded Password vulnerability in FTP function on Mitsubishi Electric Corporation MELSEC iQ-R Series EtherNet/IP module RJ71EIP91 and MELSEC iQ-F Series EtherNet/IP module FX5-ENET/IP allows a remote unauthenticated attacker to obtain a hard-coded password and access to the module via FTP.

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

A hard-coded password vulnerability exists in the FTP service of Mitsubishi Electric MELSEC iQ-R Series EtherNet/IP module RJ71EIP91 and MELSEC iQ-F Series EtherNet/IP module FX5-ENET/IP, allowing remote unauthenticated attackers to obtain the embedded credentials and gain unauthorized FTP access to the affected modules.

MitigationChange the hard-coded FTP credentials to strong, unique passwords, apply available firmware updates from Mitsubishi Electric, and disable FTP if not required or restrict network access to trusted IP addresses.

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
Fx5 Enet\/ip FirmwareOperating system
Affected:all versions
Sw1dnn Eipct Bd FirmwareOperating system
Affected:all versions
Rj71eip91 FirmwareOperating system
Affected:all versions
Sw1dnn Eipctfx5 Bd 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 installed EtherNet/IP module model
    Locate the physical module or check the system configuration for the model number - look for FX5-ENET/IP, RJ71EIP91, or the Sw1dnn EipctBd/Sw1dnn Eipctfx5Bd modules in the MELSEC iQ-R or iQ-F series PLC configuration
    Affected if The module is one of: FX5-ENET/IP, RJ71EIP91, Sw1dnn EipctBd, or Sw1dnn Eipctfx5Bd
  2. Verify FTP service is enabled on the module
    Access the module configuration via the engineering software (GX Works3 for iQ-F, GX Works3 or MR Configurator2 for iQ-R) and check the FTP settings in the EtherNet/IP module parameters. Alternatively, attempt to connect to TCP port 21 on the module IP address
    Affected if FTP service is enabled and accessible on the network
  3. Confirm the FTP credentials have not been changed from defaults
    Check the FTP user account settings in the module configuration. Compare against any documentation of custom credentials that should have been set. If the original hard-coded credentials are still in use, the system is vulnerable
    Affected if The default hard-coded FTP credentials are still configured or in use, or no custom credentials have been set
  4. Check network exposure of the FTP service
    Review firewall rules, network segmentation, and access control lists to determine if the FTP port (TCP 21) is exposed to untrusted networks or the internet
    Affected if The FTP service is reachable from untrusted network segments or directly from the internet
  5. Review FTP access logs for unauthorized access attempts
    Examine any available FTP server logs or network traffic logs for connections using default or unknown credentials, successful or failed FTP logins from unexpected IP addresses
    Affected if There are FTP connection attempts or successful logins that did not originate from authorized administrators

The environment is affected if an FX5-ENET/IP or RJ71EIP91 (or related Sw1dnn variants) EtherNet/IP module with FTP enabled is in use, and the hard-coded default FTP credentials have not been changed to unique values.

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

Change the hard-coded FTP credentials to strong, unique passwords, apply available firmware updates from Mitsubishi Electric, and disable FTP if not required or restrict network access to trusted IP addresses.

Fix this in Fx5 Enet\/ip Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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