# CVE-2018-17170: Code injection in n/a

> An attacker can inject code via a template in the Teamwire Desktop Client, leading to remote code execution on Windows systems.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jun 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-vqv6-jxc7-f43p

## What is CVE-2018-17170?

CVE-2018-17170 is a high-severity code injection vulnerability in n/a, published on 28 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Grouptime Teamwire Desktop Client 1.5.1 prior to 1.9.0 on Windows allows code injection via a template, leading to remote code execution. All backend versions prior to prod-2018-11-13-15-00-42 are affected.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Teamwire Teamwire.

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

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

## Is CVE-2018-17170 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-24275](https://insights.sbomify.com/CVE-2024-24275/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2024-24276](https://insights.sbomify.com/CVE-2024-24276/): Cross-site scripting in n/a (critical 9.6)
- [CVE-2024-24278](https://insights.sbomify.com/CVE-2024-24278/): Code injection in n/a (high 7.5)
- [CVE-2020-12621](https://insights.sbomify.com/CVE-2020-12621/): Auth bypass in n/a (medium 6.1)
- [CVE-2018-17560](https://insights.sbomify.com/CVE-2018-17560/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

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

What it is: CVE-2018-17170 is a high-severity code injection vulnerability in n/a, published on 28 Jun 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-17170 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-17170/ (Markdown: https://insights.sbomify.com/CVE-2018-17170/index.md)
```

## Sources

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

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