dbcve.org
Binisoft Windows Firewall ControlApplication · Malwarebytes

CVE-2024-25089

CRITICAL · 9.8 CVSS v3.1 Published 2024-02-04
Fix available
A fix is available. Upgrade to 6.9.9.2 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Malwarebytes Binisoft Windows Firewall Control before 6.9.9.2 allows remote attackers to execute arbitrary code via gRPC named pipes.

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

Malwarebytes Binisoft Windows Firewall Control before version 6.9.9.2 contains a vulnerability in its gRPC named pipe implementation that allows remote attackers to achieve arbitrary code execution. The application, which runs with elevated privileges to manage Windows firewall rules, does not properly validate or authenticate incoming requests through its gRPC named pipe interface, enabling an unauthenticated attacker to inject and execute malicious code on the affected system.

MitigationUpdate Malwarebytes Binisoft Windows Firewall Control to version 6.9.9.2 or later. Until patched, restrict network access to systems running this software and monitor for suspicious named pipe activity.

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
Binisoft Windows Firewall ControlApplication
Affected:< 6.9.9.2

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Malwarebytes Binisoft Windows Firewall Control is installed
    Open Programs and Features (appwiz.cpl) or check the installation directory (typically C:\Program Files\Malwarebytes\Windows Firewall Control or C:\Program Files (x86)\Binisoft\Windows Firewall Control) for the application executable (wfc.exe)
    Affected if The application is installed on the system
  2. Determine the installed version
    Right-click the executable wfc.exe, select Properties, then view the Details tab for the Product Version. Alternatively, right-click the application in Programs and Features and select Properties to view the version
    Affected if The installed version is lower than 6.9.9.2
  3. Verify the gRPC named pipe service is active
    Open Task Manager or use Tasklist.exe via command prompt to check if the Windows Firewall Control service process (wfc.exe) is running. The vulnerability can be exploited when the application's gRPC named pipe interface is accessible
    Affected if The application is running and its gRPC named pipe interface is exposed (listening on named pipe \\ pipes\\wfc_grpc)

The system is affected if Malwarebytes Binisoft Windows Firewall Control is installed with a version below 6.9.9.2 and the application is running with its gRPC named pipe service active.

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
Upgrade available Upgrade to 6.9.9.2 or later
Fixed in 6.9.9.2
Interim mitigation

Update Malwarebytes Binisoft Windows Firewall Control to version 6.9.9.2 or later. Until patched, restrict network access to systems running this software and monitor for suspicious named pipe activity.

Recommended fix Moderate confidence

Upgrade to Binisoft Windows Firewall Control version 6.9.9.2 or later

  1. Download the latest version of Binisoft Windows Firewall Control (version 6.9.9.2 or later) from the official vendor website (www.binisoft.org)
  2. Create a backup of your current firewall configuration settings if possible
  3. Uninstall the current vulnerable version of Binisoft Windows Firewall Control
  4. Install the fixed version 6.9.9.2 on the affected Windows system
  5. Restart the Windows Firewall Control service if required
  6. Verify the application is running correctly and the gRPC named pipe service is functioning
Caveat No known breaking changes documented for this version upgrade

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

Fix this in Binisoft Windows Firewall Control Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25089 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-25089 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