Loading vulnerability…
Lyris ListManager versions 5.0 through 8.9b, when using the MSDE database, configure the 'sa' account with a weak password consisting of the string 'lyris' followed by up to 5 digits, likely derived from the process ID. This predictable and short password space allows attackers to perform brute force attacks to gain administrative access to the database.
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 targeting a weak password vulnerability in Lyris ListManager's MSDE (Microsoft SQL Server Desktop Engine) installation (CVE-2005-4145). The exploit attempts to brute-force the 'sa' account password, which is set to 'lminstall' during installation or to 'lyris' followed by the installer process ID. Upon successful authentication, the module uploads and executes a custom payload (such as a reverse shell) on the target system. The attack vector is network-based, requiring access to the target's MSSQL service (typically on TCP port 1433). The module is operational and can be used to gain remote code execution on vulnerable systems. The repository structure is typical for Metasploit, with the exploit implemented in a single Ruby file under the appropriate modules directory.
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.