dbcve.org
HousecallApplication · Trendmicro

CVE-2022-38764

HIGH · 7.8 CVSS v3.1 Published 2022-09-19
Fix available
A fix is available. Upgrade to after 1.62.1.1133 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

This is a local privilege escalation vulnerability in Trend Micro HouseCall antivirus installer. The installer creates a folder with overly permissive (likely weak) access control permissions, allowing a local unprivileged attacker to potentially place malicious files or modify existing files in that folder to execute code with elevated privileges.

MitigationUpdate Trend Micro HouseCall to a version newer than 1.62.1.1133, or manually review and restrict folder permissions on existing installations to follow least-privilege principles.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
HousecallApplication
Affected:<= 1.62.1.1133

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify Trend Micro HouseCall installation exists
    Check for HouseCall installation directory in Program Files or use system inventory tools to detect the product
    Affected if HouseCall is installed on the system
  2. Determine installed HouseCall version
    Locate the HouseCall executable or version information file and read the version number
    Affected if The installed version is 1.62.1.1133 or lower
  3. Locate the HouseCall installation folder
    Find the main HouseCall installation directory, typically under Program Files or ProgramData
    Affected if A HouseCall installation folder exists on the system
  4. Inspect folder permissions for excessive access
    Right-click the HouseCall installation folder, go to Properties > Security, and examine the Access Control List (ACL) for unnecessary granted permissions to standard users or groups
    Affected if The folder grants write, modify, or full control permissions to Users, Everyone, or other unprivileged accounts
  5. Check for untrusted user modification capability
    Use 'icacls' command or Security tab to verify if non-admin users can create, modify, or delete files within the HouseCall folder
    Affected if Unprivileged users have permissions to write or modify files in the HouseCall directory

A system is affected if Trend Micro HouseCall version 1.62.1.1133 or lower is installed AND the installation folder grants write or modify permissions to unprivileged users or groups.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 1.62.1.1133
Interim mitigation

Update Trend Micro HouseCall to a version newer than 1.62.1.1133, or manually review and restrict folder permissions on existing installations to follow least-privilege principles.

Recommended fix Moderate confidence

Check with Trend Micro support or the official helpcenter.trendmicro.com for the specific fixed release version (version should be higher than 1.62.1.1133)

  1. Verify current HouseCall version by opening the application and checking About/Version information
  2. Download the latest version of Trend Micro HouseCall from the official Trend Micro download center or support website
  3. Ensure you have administrator privileges on the local machine before proceeding with installation
  4. Close any running instances of HouseCall or other Trend Micro applications
  5. Run the installer with elevated (administrator) privileges
  6. Follow the installation wizard prompts to complete the update
  7. After installation, verify the new version number matches the patched release
  8. Confirm that the installation directory permissions have been properly restricted (non-admin users should have read-only access)
Caveat Review release notes for any changes to functionality or system requirements before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Housecall Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-38764 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-38764 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data