Raw vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-29145 is a high-severity Weak Password Recovery Mechanism for Forgotten Password (CWE-640) vulnerability in Malwarebytes Endpoint Detection And Response. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Valid Accounts (T1078); ranked at the 25th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-32747
Vulnerability Data
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Establishing procedures for lost or compromised authenticators addresses weak password recovery mechanisms.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Credential lifecycle management directly includes password reset/recovery flows.
Identity proofing is the core control that prevents weak or bypassed recovery mechanisms.
Authentication policy covers strength/MFA but does not address recovery path weaknesses.
Secure SDLC reduces implementation flaws but is not specific to password-recovery design.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's combined programme (code review, static analysis, vulnerability scanning, penetration testing) reaches CWE-640 from both SOURCE and RUNTIME angles: pentesters routinely exercise password recovery flows for brute-force, token reuse, and information disclosure (the exact failure modes in the 2024-2025 CVE examples), and code review catches implementation flaws like missing throttling or returning the original password; the remainder is design-level weaknesses (e.g., security questions that are too common or guessable from social media) where the code looks reasonable and the weakness only surfaces under a review of the recovery design itself.
A.5.17(b) requires identity verification before providing new, replacement or temporary authentication information, and (c) requires secure transmission — both directly touch the recovery flow and prevent some weak-recovery designs (e.g. no verification, cleartext delivery). The clause does not address throttling on reset attempts, token invalidation after use, security-question design, or other recovery-specific weaknesses catalogued under CWE-640, so a meaningful remainder is left.
Training helps developers recognize weak recovery designs (throttling, security questions, token invalidation) but the weakness is a detailed design/implementation choice that training alone does not prevent; the stronger controls are secure coding standards and security testing, leaving training as a minority effect.
Secure-coding standards can prevent weak recovery implementations, yet the control is wider in scope.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so a well-implemented clause reduces ordinary software weaknesses in delivered code the way those practices do; CWE-640 is a regular design/implementation CWE that secure design and coding practices address, but the clause depends on those other controls being properly implemented, capping the effect at `partial`.
A.8.8's reach is disclosure-based (vulnerability scanning, CVE feeds, supplier reporting), and CWE-640 does surface as CVEs in third-party products (WordPress plugins, web conference tools, etc.), so A.8.8 finds the disclosed minority of instances; first-party custom password-recovery code that never receives a CVE is outside its reach, which is A.8.29's territory.