# CVE-2018-7239: A DLL hijacking vulnerability exists in Schneider Electric's SoMove Software and associated DTM software components in all versions prior to


- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Mar 2018
- **Updated:** 16 Sep 2024
- **Also known as:** GHSA-98p4-3pv5-4m4w

## What is CVE-2018-7239?

CVE-2018-7239 is a high-severity vulnerability in Schneider Electric SE SoMove, published on 9 Mar 2018. 

### Official description

A 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.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2018-7239?

It affects 13 products.


Products: Schneider-Electric Atv12 Dtm, Schneider-Electric Atv212 Dtm, Schneider-Electric Atv312 Dtm, Schneider-Electric Atv31 Dtm, Schneider-Electric Atv320 Dtm, Schneider-Electric Atv32 Dtm, Schneider-Electric Atv340 Dtm, Schneider-Electric Atv600 Dtm, Schneider-Electric Atv61 Dtm, Schneider-Electric Atv71 Dtm, Schneider-Electric Atv900 Dtm, Schneider-Electric Atv Lift Dtm, Schneider-Electric Somove.

## How do I fix CVE-2018-7239?

No fix has been published for CVE-2018-7239 yet. Limit exposure of the affected software until one is available.

## Is CVE-2018-7239 being exploited?

There is no known exploitation of CVE-2018-7239 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-7239 and fix it if it is affected.

What it is: CVE-2018-7239 is a high-severity vulnerability in Schneider Electric SE SoMove, published on 9 Mar 2018. 
Exploitation: There is no known exploitation of CVE-2018-7239 in the wild and no public exploit code.

Affected product: Schneider Electric SE SoMove. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2018-7239/ (Markdown: https://insights.sbomify.com/CVE-2018-7239/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2018-7239
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2018-7239
- OSV: https://osv.dev/vulnerability/CVE-2018-7239

---
From sbomify Insights: https://insights.sbomify.com/CVE-2018-7239/
Summaries are generated and may contain mistakes; the official description above is the record.