Privilege escalation via unchecked message-bus file input
Published Jan 9, 2024 · Updated Jun 17, 2025
Buffer overflow in Trellix Agent before 5.8.1 allows local users on Linux and macOS to gain root privileges or crash its service. The TA service fails to validate data written to point-product message-bus socket files before processing it, corrupting memory in the root process. A local account is required; successful exploitation can elevate privileges, interrupt the service, and disable event reporting to ePO.
Summary
What happened
Buffer overflow in Trellix Agent before 5.8.1 allows local users on Linux and macOS to gain root privileges or crash its service. The TA service fails to validate data written to point-product message-bus socket files before processing it, corrupting memory in the root process. A local account is required; successful exploitation can elevate privileges, interrupt the service, and disable event reporting to ePO.
The record
- CVE
- CVE-2024-0213
- Published
- Jan 9, 2024
- Updated
- Jun 17, 2025
- Vendor
- Trellix
- Product
- Trellix Agent
- Classifications
- CWE-120, T1068
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 9, 2024CVE publishedPublication date reported by the CVE source.
- Jun 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=Prior to 5.8.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo