# CVE-2019-15628: Other in Trend Micro Security (Consumer)

> Attackers can execute malicious code via DLL hijacking in Trend Micro Security, enabling persistence and potential privilege escalation.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/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:** 2 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-p5cv-767r-2fpm

## What is CVE-2019-15628?

CVE-2019-15628 is a high-severity vulnerability in Trend Micro Security (Consumer), published on 2 Dec 2019. 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 Security (Consumer) 2020 (v16.0.1221 and below) is affected by a DLL hijacking vulnerability that could allow an attacker to use a specific service as an execution and/or persistence mechanism which could execute a malicious program each time the service is started.

Weakness: CWE-426 (Untrusted Search Path)

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

It affects 4 products.


Products: Trendmicro Antivirus \+ Security 2020, Trendmicro Internet Security 2020, Trendmicro Maximum Security 2020, Trendmicro Premium Security 2020.

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

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

## Is CVE-2019-15628 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15628 is a high-severity vulnerability in Trend Micro Security (Consumer), published on 2 Dec 2019. 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-15628 in the wild and no public exploit code.

Affected product: Trend Micro Security (Consumer). 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-15628/ (Markdown: https://insights.sbomify.com/CVE-2019-15628/index.md)
```

## Sources

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

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