Loading vulnerability…
A stack-based buffer overflow exists in Firebird versions 2.1.3 through 2.1.5 before build 18514, and 2.5.1 through 2.5.3 before build 26623, on Windows. The vulnerability is triggered by a missing size check during the extraction of a group number from CNCT information in a crafted packet sent to TCP port 3050. This allows remote attackers to overflow a stack buffer and potentially execute arbitrary code.
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.
This repository contains a single Metasploit module (fb_cnct_group.rb) that exploits a buffer overflow vulnerability (CVE-2013-2492) in Firebird SQL Server for Windows. The exploit targets the CNCT group number field in the Firebird protocol, which is not properly bounds-checked, allowing an attacker to overwrite a pointer and execute arbitrary code. The module constructs a specially crafted packet and leverages a two-phase stack pivot and a ROP chain to bypass DEP using VirtualAlloc. The exploit is operational and allows the attacker to run arbitrary payloads (such as a shell) on the target system. The module supports multiple specific Firebird versions and uses TCP port 3050, the default for Firebird SQL Server. The only file in the repository is a Ruby script compatible with the Metasploit framework, and it is fully weaponized for remote code execution.
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.