Detection bypass via reused or colliding inode identifiers
Published Jun 30, 2023 · Updated Nov 26, 2024
Detection bypass in Malwarebytes EDR 1.0.11 for Linux allows local users to evade file monitoring via inode identifier collisions. Detection layers treat inode identifiers as stable and globally unique even though replacing a file can reuse an identifier and different filesystems can assign the same value. Low-privileged local access permits a crafted replacement or collision to make malicious file activity indistinguishable to the affected layers, without granting direct access to protected data.
Summary
What happened
Detection bypass in Malwarebytes EDR 1.0.11 for Linux allows local users to evade file monitoring via inode identifier collisions. Detection layers treat inode identifiers as stable and globally unique even though replacing a file can reuse an identifier and different filesystems can assign the same value. Low-privileged local access permits a crafted replacement or collision to make malicious file activity indistinguishable to the affected layers, without granting direct access to protected data.
The record
- CVE
- CVE-2023-29147
- Published
- Jun 30, 2023
- Updated
- Nov 26, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-290, T1562.001
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 30, 2023CVE publishedPublication date reported by the CVE source.
- Nov 26, 2024Record 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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