CVE-2023-43694
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 · uneditedAn issue was discovered in Malwarebytes 4.6.14.326 and before and 5.1.5.116 and before (and Nebula 2020-10-21 and later). An Out of bounds read in several disassembling utilities causes stability issues and denial of service.
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 confidenceAn out-of-bounds read vulnerability exists in multiple disassembling utilities within Malwarebytes versions 4.6.14.326 and prior, 5.1.5.116 and prior, and Nebula versions 2020-10-21 and later. The vulnerability allows reading memory beyond allocated buffers during disassembly operations, leading to stability issues and potential denial of service conditions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- High
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:L/AC:H/PR:H/UI:N/S:U/C:H/I:L/A:L
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.
-
Identify installed Malwarebytes consumer versionOpen Malwarebytes, go to Settings > About, or run 'mbam.exe -v' from command line to retrieve the exact version numberAffected if The version is 4.6.14.326 or lower, or 5.1.5.116 or lower
-
Identify installed Malwarebytes Nebula versionLog into the Malwarebytes Nebula console and navigate to the Account or Settings section to view the current Nebula platform versionAffected if The Nebula version is 2020-10-21 or any later version (the vulnerability affects versions from 2020-10-21 onward)
-
Determine if disassembly utilities are in useReview logs or user activity to see if the Malwarebytes disassembling or analysis features have been recently invoked. Check for any automated or manual disassembly operations.Affected if The disassembly functionality is actively used or has been triggered on the system
-
Verify affected product typeConfirm whether the installation is the standalone consumer product (version 4.x or 5.x) or the Nebula cloud platformAffected if The installed product falls within the affected version ranges for any of the three affected lines (4.6.14.326 and prior, 5.1.5.116 and prior, or Nebula 2020-10-21 and later)
The environment is affected if running Malwarebytes consumer versions 4.6.14.326 or earlier, versions 5.1.5.116 or earlier, or any Nebula version from 2020-10-21 onward, and the disassembly feature is in use.
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 dataUpdate Malwarebytes installations to versions newer than 4.6.14.326 and 5.1.5.116 respectively. For Nebula users, apply the vendor-provided patch for versions after 2020-10-21.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-43694 — 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-43694 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