# CVE-2024-36473: Path traversal in Trend Micro VPN Proxy One Pro

> Attackers can overwrite or create arbitrary files, causing local denial of service and potentially elevating privileges in Trend Micro VPN Proxy One Pro.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jun 2024
- **Updated:** 28 Mar 2025
- **Also known as:** GHSA-58pq-phhq-59vj

## What is CVE-2024-36473?

CVE-2024-36473 is a medium-severity path traversal vulnerability in Trend Micro VPN Proxy One Pro, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Trend Micro VPN Proxy One Pro, version 5.8.1012 and below is vulnerable to an arbitrary file overwrite or create attack but is limited to local Denial of Service (DoS) and under specific conditions can lead to elevation of privileges.

Weakness: CWE-73 (External Control of File Name or Path)

## Which versions are affected by CVE-2024-36473?

It affects 1 product.


Products: Trendmicro Vpn Proxy One.

## How do I fix CVE-2024-36473?

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

## Is CVE-2024-36473 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36473 and fix it if it is affected.

What it is: CVE-2024-36473 is a medium-severity path traversal vulnerability in Trend Micro VPN Proxy One Pro, published on 10 Jun 2024. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36473 in the wild and no public exploit code.

Affected product: Trend Micro VPN Proxy One Pro. 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-2024-36473/ (Markdown: https://insights.sbomify.com/CVE-2024-36473/index.md)
```

## Sources

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

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