A vulnerability in the nfsd implementation of the FreeBSD 6.0 kernel allows remote attackers to trigger a denial of service condition by sending a specially crafted NFS mount request. This issue was demonstrated using the ProtoVer NFS test suite, indicating improper input validation or handling of NFS protocol messages in the kernel's nfsd component.
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 vulnerability in FreeBSD 6.0's NFS daemon (nfsd). The module, written in Ruby, is located at 'modules/auxiliary/dos/freebsd/nfsd/nfsd_mount.rb'. It implements a network-based attack by sending a specially-crafted NFS Mount request to TCP port 2049 of a vulnerable FreeBSD 6.0 host. Successful exploitation results in a kernel panic, effectively crashing the target system and causing a denial of service. The module is operational and does not provide a customizable payload, but the crafted packet is hardcoded within the exploit. The exploit specifically targets CVE-2006-0900 and is referenced in BID 16838 and OSVDB 23511. No detection or post-exploitation features are present; the sole purpose is to crash the target system.
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.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.