CVE-2018-7239
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 · uneditedA DLL hijacking vulnerability exists in Schneider Electric's SoMove Software and associated DTM software components in all versions prior to 2.6.2 which could allow an attacker to execute arbitrary code.
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 confidenceThis is a DLL hijacking vulnerability in Schneider Electric's SoMove software (used for motor configuration and setup) and associated DTM (Device Type Manager) components. The application loads Dynamic Link Libraries from insecure paths, allowing an attacker to place a malicious DLL in a location where the application will load it, resulting in arbitrary code execution with the privileges of the affected application.
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< 12.7.0< 12.7.0< 12.7.0< 12.7.0< 12.7.0< 12.7.0< 1.1.6< 1.2.3CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Schneider Electric DTM componentsOpen Windows Control Panel, go to Programs and Features, and look for any installed software with names containing 'Atv Lift Dtm', 'Atv12 Dtm', 'Atv212 Dtm', 'Atv31 Dtm', 'Atv312 Dtm', 'Atv32 Dtm', 'Atv320 Dtm', or 'Atv340 Dtm'. Alternatively, check the installation directory where SoMove and DTM components are typically installed (commonly under C:\Program Files\Schneider Electric\SoMove\ or similar paths).Affected if Any of the eight listed DTM products are present on the system
-
Determine the installed version of each DTM componentRight-click each identified DTM entry in Programs and Features, select Properties, and view the Version field. Alternatively, right-click the main executable for each DTM (typically named similar to the product), select Properties, and check the Details tab for version information.Affected if The displayed version number is lower than 12.7.0 for Atv Lift/Atv12/Atv212/Atv31/Atv312/Atv32, lower than 1.1.6 for Atv320, or lower than 1.2.3 for Atv340
-
Verify the SoMove software versionLocate the SoMove installation directory and find the main executable (usually SoMove.exe). Right-click it, select Properties, and check the version on the Details tab. This software is required to run the DTM components.Affected if SoMove version is older than 2.6.2 (the version that includes the fix for this DLL hijacking issue)
Your environment is affected if any of the eight listed DTM components are installed with a version below the thresholds (12.7.0, 1.1.6, or 1.2.3 depending on the specific DTM), or if SoMove software is present at a version prior to 2.6.2.
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 data1.1.61.2.312.7.0
Update Schneider Electric SoMove Software and associated DTM components to version 2.6.2 or later to remediate this vulnerability.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-7239 — 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-2018-7239 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