# CVE-2022-33158: Privilege escalation in Trend Micro VPN Proxy One Pro (Consumer)

> A local attacker can exploit overly permissive folder permissions in Trend Micro VPN Proxy Pro to escalate privileges on the affected system.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/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:** 29 Jul 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-g8j6-mw28-v33x

## What is CVE-2022-33158?

CVE-2022-33158 is a high-severity vulnerability in Trend Micro VPN Proxy One Pro (Consumer), published on 29 Jul 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Trend Micro VPN Proxy Pro version 5.2.1026 and below contains a vulnerability involving some overly permissive folders in a key directory which could allow a local attacker to obtain privilege escalation on an affected system.

Weakness: CWE-552 (Files or Directories Accessible to External Parties)

## Which versions are affected by CVE-2022-33158?

It affects 1 product.


Products: Trendmicro Vpn Proxy One Pro.

## How do I fix CVE-2022-33158?

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

## Is CVE-2022-33158 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-33158 and fix it if it is affected.

What it is: CVE-2022-33158 is a high-severity vulnerability in Trend Micro VPN Proxy One Pro (Consumer), published on 29 Jul 2022. 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-2022-33158 in the wild and no public exploit code.

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

## Sources

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

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