Loading vulnerability…
A buffer overflow vulnerability exists in libxml2 due to improper enforcement of limits on port values when handling HTTP redirects. This flaw allows remote attackers to trigger a buffer overflow by supplying specially crafted input, potentially leading to 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.
This repository is a proof-of-concept exploit for CVE-2017-7376, targeting a buffer overflow vulnerability in libxml2 (v2.7.7). The exploit consists of several components: - A crafted XML file (buffer_overflow.xml) containing an XInclude directive referencing a local HTTP server. - A Node.js script (http.js) that runs a web server on 127.0.0.1:8080 and responds to any request with a 301 redirect to a URL with an excessively large port number (http://127.0.0.1:2147426192). - A C program (main.c) that loads the crafted XML file and processes XIncludes using the vulnerable libxml2 library, triggering the buffer overflow when it follows the redirect. - A patch (nanohttp.patch) to libxml2's nanohttp.c to print a message when a buffer overflow is detected, making the exploit's effect visible. - A shell script (run.sh) to set up the environment and run the exploit. The repository is structured to demonstrate the vulnerability in a controlled environment. It requires the user to download and build a vulnerable version of libxml2, apply the provided patch, and run the exploit components locally. The exploit does not provide a weaponized payload but clearly demonstrates the buffer overflow condition, making it a proof-of-concept. The main attack vector is local execution with network interaction (HTTP redirect). The endpoints involved are local HTTP URLs used to trigger the vulnerability.
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.