# CVE-2018-6766: Other in n/a

> Unauthenticated remote attackers can execute arbitrary code via DLL hijacking in Swisscom TVMediaHelper due to insecure library loading.

- **Severity:** High 7.8 (`CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Mar 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xrw6-gq4w-mj7r

## What is CVE-2018-6766?

CVE-2018-6766 is a high-severity vulnerability in n/a, published on 27 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Swisscom TVMediaHelper 1.1.0.50 contains a vulnerability that could allow an unauthenticated, remote attacker to execute arbitrary code on the targeted system. This vulnerability exists due to the way .dll files are loaded. It allows an attacker to load a .dll of the attacker's choosing that could execute arbitrary code without the user's knowledge. The specific flaw exists within the handling of several DLLs (dwmapi.dll, PROPSYS.dll, cscapi.dll, SAMLIB.dll, netbios.dll, winhttp.dll, security.dll, ntmarta.dll, WindowsCodecs.dll, apphelp.dll) loaded by the SwisscomTVMediaHelper.exe process.

Weakness: CWE-427 (Uncontrolled Search Path Element)

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

It affects 1 product.


Products: Swisscom Tvmediahelper.

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

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

## Is CVE-2018-6766 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-6766 is a high-severity vulnerability in n/a, published on 27 Mar 2018. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-6766 in the wild and no public exploit code.

Affected product: n/a. 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-6766/ (Markdown: https://insights.sbomify.com/CVE-2018-6766/index.md)
```

## Sources

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

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