A vulnerability in rpcbind (through 0.2.4), LIBTIRPC (through 1.0.1 and 1.0.2-rc through 1.0.2-rc3), and NTIRPC (through 1.4.3) allows remote attackers to cause a denial of service by sending crafted UDP packets to port 111. The affected implementations do not properly enforce maximum RPC data size limits during memory allocation for XDR strings, resulting in excessive memory consumption without subsequent freeing. This issue is also known as 'rpcbomb'.
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.
2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository contains a single Metasploit auxiliary module (modules/auxiliary/dos/rpc/rpcbomb.rb) designed to exploit a denial-of-service vulnerability (CVE-2017-8779) in certain *nix implementations of rpcbind, LIBTIRPC, and NTIRPC. The module sends repeated, specially crafted UDP packets to the target's rpcbind service (default port 111), each requesting a large memory allocation. The size and number of allocations are configurable via module options (ALLOCSIZE and COUNT). Successful exploitation can exhaust system memory, potentially crashing the rpcbind service or the host. The code is written in Ruby and leverages Metasploit's auxiliary and UDP scanner components. No detection or post-exploitation features are present; the module's sole purpose is to cause a denial of service by resource exhaustion.
This repository contains a Go-based proof-of-concept exploit for CVE-2017-8779, a denial-of-service vulnerability in rpcbind, libtirpc, and ntirpc on UNIX-like systems. The exploit is implemented in a single code file (RPCBomb.go) and is designed to send specially crafted UDP packets to the target's rpcbind service (default port 111). The payload is a large XDR string embedded in an RPC call, which causes the target service to allocate excessive memory, potentially leading to a denial of service. The exploit is configurable via command-line flags for the target host, port, number of bytes to allocate, number of packets to send, and number of concurrent threads. The repository also includes a README with usage instructions and background on the vulnerability. No hardcoded IPs or domains are present; the target is specified at runtime. The exploit is not part of a framework and is a standalone proof-of-concept.
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.