Unauthenticated code execution via gRPC named pipes
Published Feb 4, 2024 · Updated Aug 26, 2024
Code injection in Malwarebytes Windows Firewall Control before 6.9.9.2 allows remote attackers to execute arbitrary code via gRPC named pipes. The vendor identifies the gRPC named-pipe channel as the affected locus but has not published the unsafe message operation or code path. No authentication or user interaction is required; successful exploitation permits arbitrary code execution on the affected Windows host.
Summary
What happened
Code injection in Malwarebytes Windows Firewall Control before 6.9.9.2 allows remote attackers to execute arbitrary code via gRPC named pipes. The vendor identifies the gRPC named-pipe channel as the affected locus but has not published the unsafe message operation or code path. No authentication or user interaction is required; successful exploitation permits arbitrary code execution on the affected Windows host.
The record
- CVE
- CVE-2024-25089
- Published
- Feb 4, 2024
- Updated
- Aug 26, 2024
- Vendor
- Malwarebytes
- Product
- Windows Firewall Control
- Classifications
- CWE-94, T1210
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 4, 2024CVE publishedPublication date reported by the CVE source.
- Aug 26, 2024Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <6.9.9.2
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo