Loading vulnerability…
Multiple buffer overflow vulnerabilities exist in the web tool component of MySQL MaxDB versions prior to 7.5.00.26. Specifically, a remote attacker can trigger a buffer overflow by sending an HTTP GET request with an excessively long file parameter following a percent ('%') sign, or by sending a long Lock-Token string to the WebDAV functionality. The latter is due to improper handling in the getLockTokenHeader function within WDVHandler_CommonUtils.c. These flaws allow for the execution of 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.
This repository contains a single Metasploit module (maxdb_webdbm_get_overflow.rb) that exploits a stack buffer overflow vulnerability (CVE-2005-0684) in the MaxDB WebDBM service on Windows systems. The exploit works by sending a specially crafted HTTP GET request to the service, overflowing a buffer and overwriting the SEH frame to execute arbitrary code. The module supports multiple Windows targets and MaxDB versions, with hardcoded return addresses for each. The payload is customizable (up to 2052 bytes) and can be any Metasploit-compatible shellcode. The exploit assumes the MaxDB web root path matches a specific length for reliable exploitation. The only network endpoint involved is the HTTP service (default port 9999) on the target. The repository is operational and ready for use within the Metasploit framework.
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.