dbcve.org
Endpoint Detection And ResponseApplication · Malwarebytes

CVE-2023-29145

HIGH · 7.8 CVSS v3.1 Published 2023-06-30
Fix available
A fix is available. Upgrade to after 1.0.14 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
The Malwarebytes EDR 1.0.11 for Linux driver doesn't properly ensure whitelisting of executable libraries loaded by executable files, allowing arbitrary code execution. The attacker can set LD_LIBRARY_PATH, set LD_PRELOAD, or run an executable file in a debugger.

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

The Malwarebytes EDR 1.0.11 for Linux driver fails to properly enforce library whitelisting, allowing attackers to inject arbitrary code via LD_LIBRARY_PATH, LD_PRELOAD environment variables, or by running executables under a debugger. This bypasses the EDR's intended security controls and enables arbitrary code execution.

MitigationApply the vendor-supplied patch/update to Malwarebytes EDR for Linux. Until patched, monitor for unauthorized use of LD_PRELOAD/LD_LIBRARY_PATH and debugger attachment to processes.

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 Detection And ResponseApplication
Affected:<= 1.0.11
MalwarebytesApplication
Affected:<= 1.0.14

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. Identify installed Malwarebytes product and version
    Use your system's package manager or software inventory to find the installed version of Malwarebytes Endpoint Detection And Response or Malwarebytes Malwarebytes. Common commands: dpkg -l, rpm -qi, or check /var/lib/dpkg/info/ for Debian-based systems.
    Affected if The installed version is 1.0.11 or lower for Endpoint Detection And Response, or 1.0.14 or lower for Malwarebytes.
  2. Confirm the EDR driver component is loaded
    Check if the Malwarebytes EDR driver is running as a kernel module or daemon. Look for malwarebytes-related processes or kernel modules using ps, lsmod, or systemctl status.
    Affected if The vulnerable driver component is present and loaded on the system.
  3. Inspect environment variables for LD_PRELOAD or LD_LIBRARY_PATH
    Examine running processes for LD_PRELOAD or LD_LIBRARY_PATH environment variables. Use: ps auxww | grep -E 'LD_PRELOAD|LD_LIBRARY_PATH' or check /proc/<pid>/environ for suspicious values.
    Affected if LD_PRELOAD or LD_LIBRARY_PATH is set for processes protected by the EDR, indicating potential library injection.
  4. Detect debugger attachment to EDR-protected processes
    Monitor for debugger tools (gdb, strace, ltrace, ptracer) being attached to Malwarebytes EDR processes. Check process tree and look for parent processes that are debuggers.
    Affected if A debugger is attached to EDR processes, bypassing intended security controls.
  5. Review process execution logs for anomalous library loading
    Check system logs, audit logs (auditd), or EDR telemetry for processes loading libraries from unexpected paths or using LD_PRELOAD while under EDR protection.
    Affected if Arbitrary libraries are being loaded into protected processes, indicating the whitelisting bypass is being exploited.

A system is affected if it runs a vulnerable Malwarebytes product version (EDR <=1.0.11 or Malwarebytes <=1.0.14) with the EDR driver loaded, and evidence exists of library injection via environment variables or debugger attachment to protected processes.

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.

From vendor data
Upgrade available Upgrade to a release after 1.0.14
Interim mitigation

Apply the vendor-supplied patch/update to Malwarebytes EDR for Linux. Until patched, monitor for unauthorized use of LD_PRELOAD/LD_LIBRARY_PATH and debugger attachment to processes.

Fix this in Endpoint Detection And Response Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing4.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,340
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-29145 — 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-2023-29145 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