Out-of-bounds ReadWeakness · CWE-125

CVE-2023-43692

HIGH · 7.5 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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
An issue was discovered in Malwarebytes before 4.6.14.326 and before 5.1.5.116 (and Nebula 2020-10-21 and later). Out-of-bound reads in strings detection utilities lead to system crashes.

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 confidence

An out-of-bounds read vulnerability exists in the strings detection utilities of Malwarebytes before versions 4.6.14.326 and 5.1.5.116. The vulnerability allows the software to read memory outside allocated buffers when processing files or data through its string extraction functionality, leading to system crashes.

MitigationUpgrade Malwarebytes to version 4.6.14.326 or later for the 4.x branch, version 5.1.5.116 or later for the 5.x branch, or the corresponding Nebula release after 2020-10-21.

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Check if Malwarebytes is installed
    Look for Malwarebytes installation directory in Program Files (C:\Program Files\Malwarebytes or C:\Program Files (x86)\Malwarebytes) or check the Windows Programs and Features list
    Affected if Malwarebytes is found installed on the system
  2. Find installed Malwarebytes version
    Open Windows Control Panel > Programs and Features, or right-click the Malwarebytes icon and select About, or check the version in the installation folder (typically in a version.dll or similar file)
    Affected if Cannot determine the version number from the installed software
  3. Compare version against vulnerable ranges
    Compare your installed version to the affected ranges: 4.x versions below 4.6.14.326, or 5.x versions below 5.1.5.116
    Affected if Installed version is 4.x and less than 4.6.14.326, OR installed version is 5.x and less than 5.1.5.116
  4. Verify string extraction functionality is in use
    Check if Malwarebytes real-time protection or on-demand scanning features are enabled, as these invoke the string extraction functionality that triggers the vulnerable code path
    Affected if Any scanning or protection feature that processes files is active

You are affected if Malwarebytes is installed with a version below 4.6.14.326 (4.x branch) or below 5.1.5.116 (5.x branch) and you use scanning or protection features that process files through string extraction.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Malwarebytes to version 4.6.14.326 or later for the 4.x branch, version 5.1.5.116 or later for the 5.x branch, or the corresponding Nebula release after 2020-10-21.

Recommended fix High confidence

Malwarebytes 4.6.14.326 (or later) or 5.1.5.116 (or later) depending on product line; Nebula post-2020-10-21

  1. Identify which Malwarebytes product is in use (consumer, business/endpoint protection, or Nebula)
  2. For Malwarebytes Endpoint Protection (Windows/Mac): Upgrade to version 4.6.14.326 or later
  3. For Malwarebytes Endpoint Protection (standalone or bundled): Upgrade to version 5.1.5.116 or later
  4. For Malwarebytes Nebula: Upgrade to a version released after October 21, 2020 that includes the fix
  5. Verify the installed version matches or exceeds the fixed release by checking About/Version in the product interface
Caveat Standard upgrade - review release notes for any configuration or feature changes in the specific target version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-43692 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