Loading vulnerability…
Eclipse Mosquitto 1.4.14 is vulnerable to a denial of service attack where an attacker can fill the server's RAM by establishing numerous connections with large payloads during the MQTT connection phase. This attack does not require authentication, allowing unauthenticated users to exploit the vulnerability and cause the Mosquitto server to shut down due to memory exhaustion.
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 C++ proof-of-concept exploit targeting MQTT brokers, specifically referencing a vulnerability discussed in Eclipse Mosquitto (see https://bugs.eclipse.org/bugs/show_bug.cgi?id=529754). The main file, MqttExploit.cpp, implements a multi-threaded denial-of-service attack against an MQTT broker by opening up to hundreds of simultaneous TCP connections to the target's port 1883 (the default MQTT port). Each thread sends a crafted MQTT CONNECT packet followed by a large (2MB) payload and then continues to send keep-alive packets. The attack is designed to exhaust the broker's resources, potentially causing it to crash or become unresponsive. The README provides attribution and context but no additional technical details. No hardcoded IP addresses or domains are present; the target IP is provided by the user at runtime. The exploit is a standalone C++ program and does not use any exploit 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.