Bmenoc0301 FirmwareOperating system · Schneider Electric

CVE-2018-7838

HIGH · 7.5 CVSS v3.1 Published 2019-07-15
Fix available
A fix is available. Upgrade to 2.16 / 2.90 or later.
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
A CWE-119 Buffer Errors vulnerability exists in Modicon M580 CPU - BMEP582040, all versions before V2.90, and Modicon Ethernet Module BMENOC0301, all versions before V2.16, which could cause denial of service on the FTP service of the controller or the Ethernet BMENOC module when it receives a FTP CWD command with a data length greater than 1020 bytes. A power cycle is then needed to reactivate the FTP service.

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 buffer overflow vulnerability (CWE-119) in the FTP service of Modicon M580 CPU (BMEP582040) and Ethernet module (BMENOC0301) allows denial of service when processing a FTP CWD command with data exceeding 1020 bytes. The FTP service crashes and requires a power cycle to recover.

MitigationApply vendor firmware updates (V2.90+ for M580, V2.16+ for BMENOC0301). As an interim control, restrict network access to the FTP service (port 21) to prevent unauthenticated attackers from triggering the overflow.

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
Bmenoc0301 FirmwareOperating system
Affected:< 2.16
Modicon M580 Bmep584040 FirmwareOperating system
Affected:< 2.90
Modicon M580 Bmep586040 FirmwareOperating system
Affected:< 2.90
Bmeh586040 FirmwareOperating system
Affected:< 2.90
Modicon M580 Bmep581020 FirmwareOperating system
Affected:< 2.90
Modicon M580 Bmep582020 FirmwareOperating system
Affected:< 2.90
Modicon M580 Bmep582040 FirmwareOperating system
Affected:< 2.90
Modicon M580 Bmep583020 FirmwareOperating system
Affected:< 2.90

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
High

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

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 product model
    Locate the model number on the physical device label or in the device configuration software (Unity Pro or EcoStruxure). Confirm it is one of: BMENOC0301, BMEP584040, BMEP586040, BMEH586040, BMEP581020, BMEP582020, BMEP582040, or BMEP583020.
    Affected if The product model matches one of the affected models listed in the CVE.
  2. Check the firmware version
    Access the device web interface, Unity Pro/EcoStruxure engineering station, or use the device's built-in diagnostics to retrieve the current firmware version. For M580 CPUs, look for firmware version under the CPU properties. For BMENOC0301, check the Ethernet module firmware.
    Affected if The installed firmware version is below 2.90 for M580 models, or below 2.16 for BMENOC0301.
  3. Verify FTP service status
    Check the device configuration for the FTP server settings. In Unity Pro or EcoStruxure, navigate to the device communication settings. Alternatively, attempt to connect to the device on port 21 (FTP) from an authorized host to confirm the service is running.
    Affected if The FTP service is enabled and running on the device.
  4. Assess network exposure of FTP port
    Perform a port scan or check firewall rules to determine if port 21 is accessible from untrusted networks. Verify whether the device FTP port is exposed to the internet or unauthorized internal segments.
    Affected if Port 21 (FTP) is accessible from networks where untrusted users could send crafted CWD commands.

You are affected if your device is one of the listed models, runs firmware below 2.90 (M580) or 2.16 (BMENOC0301), has FTP service enabled, and the FTP port is network-accessible to untrusted users.

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
Upgrade available Upgrade to 2.16 / 2.90 or later
Fixed in 2.162.90
Interim mitigation

Apply vendor firmware updates (V2.90+ for M580, V2.16+ for BMENOC0301). As an interim control, restrict network access to the FTP service (port 21) to prevent unauthenticated attackers from triggering the overflow.

Fix this in Bmenoc0301 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,620
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2018-7838 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2018-7838 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