Loading vulnerability…
SAP MaxDB 7.6.03 build 007 and earlier is vulnerable to command injection via the exec_sdbinfo and other unspecified commands. The vulnerability arises because user-supplied input containing shell metacharacters such as '&&' is not properly sanitized before being passed to cons.exe, allowing attackers to execute arbitrary commands on the underlying 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 (1 hidden).
This repository contains a single Metasploit auxiliary module targeting SAP MaxDB's cons.exe service. The module exploits a remote command injection vulnerability (CVE-2008-0244) by sending crafted TCP packets to the MaxDB service, allowing arbitrary OS command execution on the target server. The exploit connects to the target on TCP port 7210 (default), retrieves version information, and then sends a payload containing the user-specified command. The result of the command is returned to the attacker. The module is written in Ruby and is structured according to Metasploit conventions, with options for specifying the target port and command. No hardcoded IPs, URLs, or file paths are present, but the exploit is fingerprintable by its use of TCP port 7210 and the MaxDB protocol. The exploit is operational and can be used to gain command execution on vulnerable SAP MaxDB installations.
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.