GHOST is a heap-based buffer overflow in the GNU C Library's __nss_hostname_digits_dots function, reachable through gethostbyname and gethostbyname2. A faulty buffer-size calculation permits an attacker-controlled hostname to overwrite up to four bytes of adjacent heap memory. It affects glibc versions 2.2 through 2.17; applications statically linked with an affected glibc remain vulnerable even after the system library is updated.
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 (4 hidden).
This repository contains a single Metasploit module: 'exim_gethostbyname_bof.rb', which exploits the GHOST vulnerability (CVE-2015-0235) in the GNU C Library's gethostbyname functions. The exploit targets Linux systems running the Exim mail server with a vulnerable version of glibc. It works by sending specially crafted SMTP HELO commands to the target's SMTP service (typically on TCP port 25), triggering a heap-based buffer overflow and enabling remote code execution as the Exim user. The module includes both a vulnerability check and exploitation routines, and allows the attacker to execute arbitrary shell commands on the compromised system. The code is written in Ruby and is designed to be used within the Metasploit framework. No hardcoded IPs, domains, or file paths are present; the main fingerprintable endpoint is the target's SMTP service.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.