Loading vulnerability…
A buffer overflow vulnerability exists in the dbm and shm session cache code of mod_ssl before 2.8.7-1.3.23 and Apache-SSL before 1.3.22+1.46. The vulnerability is due to improper memory initialization when using the i2d_SSL_SESSION function. Remote attackers can exploit this by presenting a large client certificate, signed by a trusted CA, which results in a large serialized session and triggers the overflow, potentially allowing arbitrary code execution.
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 C exploit (764.c) and a README. The exploit is a classic remote buffer overflow targeting Apache mod_ssl (versions < 2.8.7) with vulnerable OpenSSL libraries, known as 'OpenFuck'. The exploit works by sending specially crafted SSL handshake messages to the target server, exploiting a buffer overflow to execute shellcode and spawn a remote shell. The code includes a large table of target architectures and function addresses, which must be matched to the target system (often requiring the attacker to know the address of the 'free' function in the target's httpd binary). The README provides compilation instructions and references to further documentation. The exploit is operational and requires network access to the target's HTTPS port (default 443). No hardcoded IPs or domains are present, but the exploit is highly configurable for different Linux distributions and Apache/OpenSSL versions.
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.