CVE-2023-2060
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 · uneditedWeak Password Requirements 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 access to the module via FTP by dictionary attack or password sniffing.
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 confidenceThe FTP function in Mitsubishi Electric MELSEC iQ-R Series (RJ71EIP91) and MELSEC iQ-F Series (FX5-ENET/IP) EtherNet/IP modules has weak password requirements, enabling remote unauthenticated attackers to perform dictionary attacks or sniff FTP credentials to gain unauthorized access to the module.
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 dataall versionsall versionsall versionsall versionsCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed EtherNet/IP module modelAccess the device configuration or network management interface and confirm the model number matches one of the affected products: RJ71EIP91, FX5-ENET/IP, or their BD variants (Sw1dnn-Eipct-Bd, Sw1dnn-Eipctfx5-Bd)Affected if The installed module is any version of RJ71EIP91, FX5-ENET/IP, or related BD firmware variants
-
Verify if FTP service is enabledCheck the module configuration settings via its web interface or management console for FTP server status. Use network scanning tools (such as nmap) to detect if port 21 is open and responding on the module IP addressAffected if FTP is enabled and accessible on the network
-
Inspect FTP user account password configurationAccess the module user management or FTP configuration settings and examine the configured FTP account passwords. Assess whether passwords meet complexity requirements (minimum length, mixed character types) or appear in common password dictionariesAffected if FTP user accounts use weak, short, or dictionary-based passwords
-
Check FTP traffic exposureMonitor network traffic to or from the module on port 21 using packet capture tools (such as Wireshark or tcpdump) to detect unencrypted FTP credential transmissionAffected if FTP credentials are transmitted in plaintext over the network or the module accepts anonymous/unauthenticated FTP connections
The environment is affected if a Mitsubishi Electric RJ71EIP91, FX5-ENET/IP, or related EtherNet/IP module is present, FTP is enabled, and either weak passwords are configured or FTP traffic is unencrypted and exposed.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement strong password policies (high complexity, length requirements) and consider disabling FTP if unused, or deploying the modules within a segmented network to reduce exposure to unauthenticated remote attackers.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2060 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2060 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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