Endpoint SecurityApplication · Trellix

CVE-2022-4326

MEDIUM · 6.0 CVSS v3.1 Published 2022-12-16
Fix available
A fix is available. Upgrade to 35.31.22 or later.
See remediation →
62/100
Remediation priority · Elevated
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
Improper preservation of permissions vulnerability in Trellix Endpoint Agent (xAgent) prior to V35.31.22 on Windows allows a local user with administrator privileges to bypass the product protection to uninstall the agent via incorrectly applied permissions in the removal protection functionality.

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 · high confidence

A local administrator can bypass the uninstall protection in Trellix xAgent on Windows due to incorrectly applied permissions in the removal protection functionality. This allows unauthorized removal of the endpoint security agent, compromising system protection.

MitigationUpgrade Trellix Endpoint Agent (xAgent) to version V35.31.22 or later to resolve the improper permission handling in the uninstall protection feature.

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
Endpoint SecurityApplication
Affected:< 35.31.22

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
High
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:U/C:N/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. Identify installed Trellix Endpoint Security version
    Open Windows Control Panel > Programs and Features, or run 'Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | DisplayName, DisplayVersion' in PowerShell to list installed software and locate Trellix Endpoint Security or xAgent
    Affected if The displayed version number is lower than 35.31.22
  2. Check Trellix agent service version via command line
    Open an elevated command prompt and run 'sc query' to list services, then run 'sc qc <service_name>' for the Trellix xAgent service (typically named 'McAfee Endpoint Security' or similar), or check the executable version in the Trellix installation directory
    Affected if The service version or executable version shown is prior to 35.31.22
  3. Verify uninstall protection configuration status
    Open Trellix Endpoint Security console or ePolicy Orchestrator (ePO) console to view agent policy settings, specifically looking for 'Uninstall Protection' or 'Removal Protection' settings under endpoint protection policies
    Affected if Uninstall protection is enabled and the agent version is below 35.31.22, making the permission bypass applicable

You are affected if the installed Trellix Endpoint Security or xAgent version is lower than 35.31.22 and uninstall protection is enabled, as the permission bypass vulnerability can be exploited.

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 35.31.22 or later
Fixed in 35.31.22
Interim mitigation

Upgrade Trellix Endpoint Agent (xAgent) to version V35.31.22 or later to resolve the improper permission handling in the uninstall protection feature.

Recommended fix High confidence

V35.31.22

  1. Identify all Windows systems with Trellix Endpoint Agent (xAgent) installed
  2. Check the current version of xAgent on each system (version should be < 35.31.22 to be vulnerable)
  3. Upgrade Trellix Endpoint Agent (xAgent) to version 35.31.22 or later
  4. Verify the upgrade was successful by confirming the installed version is 35.31.22 or higher

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

Fix this in Endpoint Security Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-4326 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