# CVE-2019-19691: Information disclosure in Trend Micro Apex One and OfficeScan

> An attacker with admin privileges can expose masked credential keys by manipulating page elements in Trend Micro Apex One and OfficeScan.

- **Severity:** Medium 4.9 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Dec 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-hp44-w352-x4mm

## What is CVE-2019-19691?

CVE-2019-19691 is a medium-severity vulnerability in Trendmicro Apex One, published on 20 Dec 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A vulnerability in Trend Micro Apex One and OfficeScan XG could allow an attacker to expose a masked credential key by manipulating page elements using development tools. Note that the attacker must already have admin/root privileges on the product console to exploit this vulnerability.

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

It affects 2 products.


Products: Trendmicro Apex One, Trendmicro Officescan.

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

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

## Is CVE-2019-19691 being exploited?

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

## Other vulnerabilities in Trendmicro Apex One

- [CVE-2020-8599](https://insights.sbomify.com/CVE-2020-8599/): Trend Micro Apex One and OfficeScan Authentication Bypass (critical 9.8, exploited in the wild)
- [CVE-2025-54948](https://insights.sbomify.com/CVE-2025-54948/): Trend Micro Apex One OS Command Injection (critical 9.4, exploited in the wild)
- [CVE-2021-36741](https://insights.sbomify.com/CVE-2021-36741/): Trend Micro Multiple Products Improper Input Validation (high 8.8, exploited in the wild)
- [CVE-2020-8467](https://insights.sbomify.com/CVE-2020-8467/): Trend Micro Apex One and OfficeScan Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2020-8468](https://insights.sbomify.com/CVE-2020-8468/): Trend Micro Multiple Products Content Validation Escape (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-19691 is a medium-severity vulnerability in Trendmicro Apex One, published on 20 Dec 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-19691 in the wild and no public exploit code.

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

## Sources

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

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