Loading vulnerability…
A denial-of-service vulnerability exists in qubes-mirage-firewall (Mirage firewall for QubesOS) versions 0.8.x through 0.8.3, due to excessive logging when handling large multicast UDP packets. When a guest OS user sends a crafted UDP packet to a multicast address (224.0.0.0/4), the firewall attempts to log the packet details. The logging mechanism, implemented via Solo5's Xen console, cannot handle log messages exceeding 2048 bytes, causing the process to enter a loop and consume nearly all CPU resources, halting packet forwarding for all Qubes attached to the firewall. The root cause is in the add_nat_and_forward_ipv4 function and the Nat_packet.pp logging routine. The issue is not present in version 0.7.1 and was introduced during the transition from Mini-OS to Solo5 and from PV to PVH virtualization.
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 a denial of service (DoS) vulnerability (CVE-2022-46770) in the Mirage firewall for QubesOS versions 0.8.0 to 0.8.3. The module, written in Ruby, leverages the Metasploit framework's UDP and DoS components. It allows an attacker to send a randomly sized and randomly generated UDP datagram to a specified or random IP address and UDP port, with the goal of crashing the Mirage firewall service. The module registers options for the target address (RHOST) and port (RPORT), defaulting to random multicast addresses and ports if not specified. The exploit is operational and can be used to demonstrate or test the DoS vulnerability. No hardcoded endpoints are present; the attacker must supply the target's network details. The repository is structured as a single Metasploit module file under the expected directory for auxiliary DoS modules.
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.