Loading vulnerability…
CVE-2016-7144 is a vulnerability in UnrealIRCd (before 3.2.10.7 and 4.x before 4.0.6) within the m_authenticate function in modules/m_sasl.c. The flaw allows remote attackers to spoof certificate fingerprints by sending a crafted AUTHENTICATE parameter, enabling them to log in as another user. This undermines the integrity of the authentication process, as the server incorrectly associates the attacker's session with the victim's certificate fingerprint.
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.
Repository contains a single Python script (exploit.py) implementing a network-based proof-of-concept against an IRC server’s SASL authentication flow. The script opens a TCP socket to a hardcoded target (192.168.247.x:6667), performs a minimal IRC registration and capability negotiation (CAP REQ :sasl, NICK/USER), initiates SASL with AUTHENTICATE PLAIN, then sends an oversized AUTHENTICATE parameter consisting of 500 'A' characters. It then sends CAP END and listens for responses, replying to server PINGs with PONG, and treats a closed connection as potential crash/DoS success. No vulnerability identifier (CVE) or specific IRC daemon is named; the intended effect appears to be denial-of-service via malformed/oversized SASL AUTHENTICATE handling rather than 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.