CVE-2023-29147 in EDRinfo

Summary

by MITRE • 07/01/2023

In Malwarebytes EDR 1.0.11 for Linux, it is possible to bypass the detection layers that depend on inode identifiers, because an identifier may be reused when a file is replaced, and because two files on different filesystems can have the same identifier.

Be aware that VulDB is the high quality source for vulnerability data.

Analysis

by VulDB Data Team • 12/08/2025

The vulnerability identified as CVE-2023-29147 affects Malwarebytes Endpoint Detection and Response version 1.0.11 for Linux systems, presenting a significant bypass opportunity within the security monitoring framework. This flaw specifically targets the inode-based detection mechanisms that form a critical component of the endpoint protection strategy. Inode identifiers serve as unique references within filesystems that help track and monitor file operations, making them essential for detecting suspicious activities and potential malware execution patterns.

The technical root cause of this vulnerability stems from the improper handling of inode identifiers across different filesystem contexts. When files are replaced or deleted and recreated, the filesystem may assign the same inode number to the new file, creating a scenario where the security monitoring system cannot distinguish between the original and replacement file based on inode alone. Additionally, the vulnerability extends to cases where files residing on different filesystems may inadvertently share identical inode identifiers, particularly when those filesystems are mounted or accessed in ways that compromise the uniqueness guarantee typically associated with inode numbers.

This flaw directly impacts the operational security posture of systems relying on Malwarebytes EDR, as it allows adversaries to evade detection mechanisms that depend on inode tracking. The bypass capability means that malicious actors can potentially replace legitimate files with malware while maintaining the same inode identifier, effectively hiding their activities from the monitoring system. This vulnerability represents a classic case of insufficient validation of unique identifiers and improper assumptions about filesystem behavior, which aligns with CWE-1257 - Improper Validation of Filesystem Identifiers and CWE-22 - Improper Limitation of a Pathname to a Restricted Directory.

The operational impact of this vulnerability extends beyond simple detection bypass, potentially enabling more sophisticated attack patterns where threat actors can maintain persistence while avoiding detection. Attackers may leverage this weakness to replace system binaries with malicious versions, knowing that the replacement process will not trigger alerts based on inode changes. The vulnerability creates a window of opportunity for privilege escalation attacks, where adversaries can manipulate file system structures to maintain access while remaining undetected by the EDR solution. This represents a significant concern within the ATT&CK framework under the T1059.001 - Command and Scripting Interpreter: PowerShell technique category, where such bypasses can enable more effective execution of malicious payloads.

Organizations utilizing Malwarebytes EDR should immediately implement mitigations including enhanced monitoring of file replacement events, implementation of additional verification mechanisms beyond inode numbers, and consideration of alternative file tracking methods such as file hash validation or extended attribute monitoring. The recommended approach involves strengthening the detection logic to account for inode reuse scenarios and implementing comprehensive file integrity monitoring that does not rely solely on inode identifiers. System administrators should also consider deploying additional security controls such as file system access monitoring, process behavior analysis, and network-based detection mechanisms to compensate for the weakened inode-based detection layer. Regular security assessments should include verification of filesystem identifier handling across all endpoint protection solutions to prevent similar vulnerabilities from compromising overall security posture.

Reservation

03/31/2023

Disclosure

07/01/2023

Moderation

accepted

EPSS

0.00281

KEV

no

Activities

very low

Sources

Do you know our Splunk app?

Download it now for free!