Somachine BasicApplication · Schneider Electric

CVE-2018-7823

MEDIUM · 5.3 CVSS v3.1 Published 2019-05-22
Fix available
A fix is available. Upgrade to 1.10.0.0 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
A Environment (CWE-2) vulnerability exists in SoMachine Basic, all versions, and Modicon M221(all references, all versions prior to firmware V1.10.0.0) which could cause remote launch of SoMachine Basic when sending crafted ethernet message.

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 · moderate confidence

A CWE-2 (Environment) vulnerability in SoMachine Basic and Modicon M221 PLCs allows remote launch of the software via crafted ethernet messages. The vulnerability exists in all versions of SoMachine Basic and all Modicon M221 firmware versions prior to V1.10.0.0. An attacker on the network can send specially crafted ethernet packets to trigger unauthorized remote execution.

MitigationUpgrade Modicon M221 firmware to V1.10.0.0 or later. Additionally, network segmentation and filtering of unauthorized ethernet traffic to PLCs should be implemented to reduce attack surface.

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
Somachine BasicApplication
Affected:all versions
Modicon M221 FirmwareOperating system
Affected:< 1.10.0.0

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. Check if SoMachine Basic software is installed
    On the engineering workstation, navigate to Programs and Features (Windows) or check common installation paths like C:\Program Files\Schneider Electric\SoMachine Basic to verify if SoMachine Basic is present on the system.
    Affected if SoMachine Basic is installed on the machine (all versions are affected)
  2. Identify Modicon M221 PLC on the network
    Use network scanning tools or check PLC network configuration to identify any Modicon M221 controllers accessible on the industrial network. Access the PLC web server or use Schneider Electric diagnostic tools to query the device.
    Affected if A Modicon M221 PLC is present and reachable on the network
  3. Check Modicon M221 firmware version
    Connect to the PLC via its web interface or use SoMachine Basic/SoMove software to query the firmware version. The firmware version is typically displayed in the PLC properties or device information section.
    Affected if The PLC firmware version is lower than 1.10.0.0 (for example, 1.9.x, 1.8.x, etc.)
  4. Verify ethernet communication is enabled
    Check the PLC configuration in SoMachine Basic or via the web interface to confirm that ethernet/IP communication modules are enabled and configured for network communication.
    Affected if Ethernet communication is enabled and the PLC is configured for network access

You are affected if SoMachine Basic is installed OR if a Modicon M221 PLC with firmware below version 1.10.0.0 is present on an accessible network with ethernet communication enabled.

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 1.10.0.0 or later
Fixed in 1.10.0.0
Interim mitigation

Upgrade Modicon M221 firmware to V1.10.0.0 or later. Additionally, network segmentation and filtering of unauthorized ethernet traffic to PLCs should be implemented to reduce attack surface.

Fix this in Somachine Basic Scoped from the published advisory
  • Consultation6.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,910
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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