# CVE-2017-3907: McAfee Threat Intelligence Exchange (TIE) Server - Code Injection vulnerability

> Remote attackers can execute arbitrary HTML code via the ePO extension in McAfee TIE Server, potentially compromising the web interface.

- **Severity:** Medium 5.4 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jun 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-xjmv-7wr2-r7c4

## What is CVE-2017-3907?

CVE-2017-3907 is a medium-severity code injection vulnerability in McAfee Threat Intelligence Exchange (TIE) Server, published on 13 Jun 2018. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Code Injection vulnerability in the ePolicy Orchestrator (ePO) extension in McAfee Threat Intelligence Exchange (TIE) Server 2.1.0 and earlier allows remote attackers to execute arbitrary HTML code to be reflected in the response web page via unspecified vector.

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

## Which versions are affected by CVE-2017-3907?

It affects 1 product.


Products: Mcafee Mcafee Threat Intelligence Exchange.

## How do I fix CVE-2017-3907?

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

## Is CVE-2017-3907 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-3907 and fix it if it is affected.

What it is: CVE-2017-3907 is a medium-severity code injection vulnerability in McAfee Threat Intelligence Exchange (TIE) Server, published on 13 Jun 2018. 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-2017-3907 in the wild and no public exploit code.

Affected product: McAfee Threat Intelligence Exchange (TIE) Server. 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-2017-3907/ (Markdown: https://insights.sbomify.com/CVE-2017-3907/index.md)
```

## Sources

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

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