# CVE-2023-29145: Security feature bypass in n/a

> Attackers can bypass library whitelisting in Malwarebytes EDR for Linux to execute arbitrary code via environment variables or debuggers.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 30 Jun 2023
- **Updated:** 26 Nov 2024
- **Also known as:** GHSA-pmmp-296p-3p5g

## What is CVE-2023-29145?

CVE-2023-29145 is a high-severity vulnerability in n/a, published on 30 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password)

## Which versions are affected by CVE-2023-29145?

It affects 2 products.


Products: Malwarebytes Endpoint Detection and Response, Malwarebytes Malwarebytes.

## How do I fix CVE-2023-29145?

No fix has been published for CVE-2023-29145 yet. Limit exposure of the affected software until one is available.

## Is CVE-2023-29145 being exploited?

There is no known exploitation of CVE-2023-29145 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2023-29147](https://insights.sbomify.com/CVE-2023-29147/): Security feature bypass in n/a (medium 5.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-29145 and fix it if it is affected.

What it is: CVE-2023-29145 is a high-severity vulnerability in n/a, published on 30 Jun 2023. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-29145 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2023-29145/ (Markdown: https://insights.sbomify.com/CVE-2023-29145/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2023-29145
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2023-29145
- OSV: https://osv.dev/vulnerability/CVE-2023-29145

---
From sbomify Insights: https://insights.sbomify.com/CVE-2023-29145/
Summaries are generated and may contain mistakes; the official description above is the record.