# CVE-2019-14688: Other in Trend Micro IM Security (IMS), Trend Micro Control Manager (TMCM), Trend Micro OfficeScan (OSCE), Trend Micro Endpoint Sensor (TMES), Trend Micro Security (Consumer), Trend Micro ScanMail for Microsoft Exchange (SMEX), Trend Micro ServerProtect (SP), Trend Micro Mobile Security Enterprise (TMMS Enterprise)

> Attackers can execute arbitrary code during installation if users download malicious DLLs, affecting multiple Trend Micro security products.

- **Severity:** High 7.0 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 20 Feb 2020
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-g7xx-c9x7-78fj

## What is CVE-2019-14688?

CVE-2019-14688 is a high-severity vulnerability in Trendmicro Officescan, published on 20 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Trend Micro has repackaged installers for several Trend Micro products that were found to utilize a version of an install package that had a DLL hijack vulnerability that could be exploited during a new product installation. The vulnerability was found to ONLY be exploitable during an initial product installation by an authorized user. The attacker must convince the target to download malicious DLL locally which must be present when the installer is run.

Weakness: CWE-427 (Uncontrolled Search Path Element)

## Which versions are affected by CVE-2019-14688?

It affects 8 products.


Products: Trendmicro Control Manager, Trendmicro Endpoint Sensor, Trendmicro Im Security, Trendmicro Mobile Security, Trendmicro Officescan, Trendmicro Scanmail, Trendmicro Security, Trendmicro Serverprotect.

## How do I fix CVE-2019-14688?

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

## Is CVE-2019-14688 being exploited?

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

## Other vulnerabilities in Trendmicro Officescan

- [CVE-2018-10511](https://insights.sbomify.com/CVE-2018-10511/): Server-side request forgery in Trend Micro Control Manager (critical 10.0)
- [CVE-2018-10510](https://insights.sbomify.com/CVE-2018-10510/): Path traversal in Trend Micro Control Manager (critical 9.8)
- [CVE-2018-3601](https://insights.sbomify.com/CVE-2018-3601/): Auth bypass in Trend Micro Control Manager (critical 9.8)
- [CVE-2017-11383](https://insights.sbomify.com/CVE-2017-11383/): SQL injection in n/a (critical 9.8)
- [CVE-2017-11384](https://insights.sbomify.com/CVE-2017-11384/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-14688 and fix it if it is affected.

What it is: CVE-2019-14688 is a high-severity vulnerability in Trendmicro Officescan, published on 20 Feb 2020. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2019-14688 in the wild and no public exploit code.

Affected product: Trendmicro Officescan. 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-2019-14688/ (Markdown: https://insights.sbomify.com/CVE-2019-14688/index.md)
```

## Sources

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

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