CVE-2023-27469
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 · uneditedMalwarebytes Anti-Exploit 4.4.0.220 is vulnerable to arbitrary file deletion and denial of service via an ALPC message in which FullFileNamePath lacks a '\0' character.
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 · moderate confidenceMalwarebytes Anti-Exploit 4.4.0.220 contains a vulnerability in its ALPC (Advanced Local Procedure Call) message handling where the FullFileNamePath parameter is not properly null-terminated with a '\0' character. This allows a local attacker to perform arbitrary file deletion or cause a denial of service condition by sending specially crafted ALPC messages.
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<= 4.4.0.220CVSS 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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Malwarebytes Anti-Exploit installationCheck for the presence of Malwarebytes Anti-Exploit by looking in Program Files folder (C:\Program Files\Malwarebytes\Anti-Exploit) or check Windows Programs and FeaturesAffected if The product is installed on the system
-
Identify installed versionLocate the version information in the product's executable or installer. Check the file properties of mbam.exe or look in the Windows Registry under HKLM\SOFTWARE\Malwarebytes\Anti-Exploit or HKLM\SOFTWARE\WOW6432Node\Malwarebytes\Anti-Exploit for the Version valueAffected if The version cannot be determined or the product is not found
-
Compare against affected version rangeCompare the installed version number to 4.4.0.220 - any version equal to or lower than 4.4.0.220 is affectedAffected if Installed version is 4.4.0.220 or any earlier version (e.g., 4.4.0.218, 4.3.0.200, etc.)
-
Confirm product is activeCheck if the Malwarebytes Anti-Exploit service (mbam.exe or mbamservice.exe) is running via Task Manager or Services consoleAffected if The vulnerable product version is installed and the service is running
The system is affected if Malwarebytes Anti-Exploit version 4.4.0.220 or any earlier version is installed and running on the machine.
Generated from the published advisory. Verify against your own configuration.
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 dataApply the vendor-supplied patch or upgrade to a version that addresses this vulnerability. As this is a local attack vector, minimize the attack surface by enforcing least-privilege user accounts and ensuring proper endpoint protection policies.
- Consultation3.0 h
- Implementation10.0 h
- Testing5.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-27469 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-27469 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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