SomachineApplication · Schneider Electric

CVE-2014-9200

HIGH · 7.5 CVSS v2.0 Published 2015-02-01
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
Stack-based buffer overflow in an unspecified DLL file in a DTM development kit in Schneider Electric Unity Pro, SoMachine, SoMove, SoMove Lite, Modbus Communication Library 2.2.6 and earlier, CANopen Communication Library 1.0.2 and earlier, EtherNet/IP Communication Library 1.0.0 and earlier, EM X80 Gateway DTM (MB TCP/SL), Advantys DTM for OTB, Advantys DTM for STB, KINOS DTM, SOLO DTM, and Xantrex DTMs allows remote attackers to execute arbitrary code via unspecified vectors.

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

Stack-based buffer overflow in an unspecified DLL file within DTM (Device Type Manager) development kit components used across multiple Schneider Electric industrial automation software products, including Unity Pro, SoMachine, SoMove, and various communication libraries (Modbus, CANopen, EtherNet/IP). The vulnerability allows remote attackers to execute arbitrary code via unspecified vectors.

MitigationApply vendor-supplied patches or updates from Schneider Electric for all affected products. If no patch is available, implement network segmentation and access controls to limit exposure of affected systems to untrusted networks, as the attack vector is remote and exploitable.

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
SomachineApplication
Affected:all versions
SomoveApplication
Affected:all versions
Somove LiteApplication
Affected:all versions
Unity ProApplication
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
Authentication
None
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:N/C:P/I:P/A:P

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 installed Schneider Electric industrial software
    Check for presence of Unity Pro, SoMachine, SoMove, or SoMove Lite on the system by reviewing installed programs in Add/Remove Programs or Program Files directory
    Affected if Any of these four products are installed on the system
  2. Locate DTM development kit components
    Search for directories or files related to DTM (Device Type Manager) in the product installation folders, typically found under the main product installation directory
    Affected if DTM folders or DTM-related files are present alongside the affected product installation
  3. Identify running industrial communication services
    Review running Windows services or processes related to Modbus, CANopen, or EtherNet/IP communication libraries that may leverage the DTM component
    Affected if Industrial communication services or drivers for Modbus, CANopen, or EtherNet/IP are active
  4. Check for exposed network services
    Use netstat or similar tools to identify listening ports on the system that may be accepting connections for industrial protocol communications
    Affected if Ports associated with Modbus (502), EtherNet/IP (44818), or other industrial protocols are open and listening

A system is affected if any of the four products (Unity Pro, SoMachine, SoMove, SoMove Lite) are installed and the DTM development kit components are present, regardless of version since all versions are vulnerable.

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

Apply vendor-supplied patches or updates from Schneider Electric for all affected products. If no patch is available, implement network segmentation and access controls to limit exposure of affected systems to untrusted networks, as the attack vector is remote and exploitable.

Fix this in Somachine Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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