Loading vulnerability…
MicroHttpServer (Micro HTTP Server) through version 4398570 contains a stack-based buffer overflow in the _ReadStaticFiles function in lib/middleware.c. A long URI can overflow a stack buffer, potentially enabling remote 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 minimal proof-of-concept exploit consisting of two files: a README describing CVE-2023-50965 as a Linux stack buffer overflow leading to RCE, and a single C source file implementing the exploit delivery logic. The code opens a TCP socket to 127.0.0.1 on port 8001 and sends a crafted HTTP GET request whose path contains 148 bytes of padding, a hardcoded 4-byte return address overwrite (0xffffcc60), a 32-byte NOP sled, and a placeholder shellcode buffer. The request ends with a simple HTTP/1.1 header including Host: localhost:8001. After sending the payload, the program reads a response and exits. The exploit’s main capability is network-based delivery of a classic stack overflow payload against a vulnerable HTTP service. However, the included shellcode is empty, so the repository is best classified as a POC demonstrating exploit structure rather than a complete operational RCE exploit. The hardcoded return address and localhost targeting also indicate it is intended for lab use or exploit development practice rather than generalized deployment.
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.