Loading vulnerability…
A stack-based buffer overflow exists in B Labs Bopup Communication Server version 3.2.26.5460. The vulnerability is triggered by sending a specially crafted request to TCP port 19810, which can cause a buffer overflow on the stack, potentially allowing remote attackers to execute arbitrary code on the affected system.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (2 hidden).
This repository contains a single Metasploit module (modules/exploits/windows/misc/bopup_comm.rb) that exploits a stack buffer overflow vulnerability (CVE-2009-2227) in Bopup Communications Server version 3.2.26.5460. The exploit works by sending a specially crafted packet to TCP port 19810 on the target server, causing a buffer overflow and allowing arbitrary code execution. The module is operational and allows the user to select a Metasploit payload (up to 417 bytes, with specific bad characters filtered). The exploit is network-based and targets Windows systems running the vulnerable Bopup Communications Server. The only endpoints referenced are the TCP service on port 19810 and the vendor's product URL for reference. The code is written in Ruby and follows the standard Metasploit module structure.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.