# CVE-2022-38764: Privilege escalation in Trend Micro HouseCall (Consumer)

> A local attacker can escalate privileges due to overly permissive folder permissions in the Trend Micro HouseCall installer.

- **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:** 19 Sep 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-9mr7-mh8x-48fh

## What is CVE-2022-38764?

CVE-2022-38764 is a high-severity vulnerability in Trend Micro HouseCall (Consumer), published on 19 Sep 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

A vulnerability on Trend Micro HouseCall version 1.62.1.1133 and below could allow a local attacker to escalate privlieges due to an overly permissive folder om the product installer.

Weakness: CWE-276 (Incorrect Default Permissions)

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

It affects 1 product.


Products: Trendmicro Housecall.

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

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

## Is CVE-2022-38764 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-38764 is a high-severity vulnerability in Trend Micro HouseCall (Consumer), published on 19 Sep 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-38764 in the wild and no public exploit code.

Affected product: Trend Micro HouseCall (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-38764/ (Markdown: https://insights.sbomify.com/CVE-2022-38764/index.md)
```

## Sources

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

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