Loading vulnerability…
CVE-2010-5301 is a stack-based buffer overflow vulnerability in Kolibri 2.0. The vulnerability is triggered when a remote attacker sends a HEAD request with an excessively long URI, causing a buffer overflow on the stack. This can allow the attacker to overwrite critical stack data, including the return address, 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 (1 hidden).
This repository contains a proof-of-concept exploit for CVE-2010-5301, a stack-based buffer overflow in Senkas Kolibri HTTP Server 2.0 on Windows. The exploit (poc.py) is a Python script that targets the HTTP server by sending a specially crafted HEAD request to the server's TCP port (default 8080). The exploit achieves code execution by overflowing the SEH chain and redirecting execution to an egghunter shellcode, which then locates and executes a custom shellcode payload delivered in the User-Agent header. The exploit also demonstrates DLL injection, where an arbitrary DLL is dropped to disk and used to provide a nullbyte-free POP-POP-RET address for SEH overwrite. The exploit requires the attacker to specify the PID of the target process, indicating a need for local or privileged access. The repository consists of a README.md (detailed explanation and references), an images directory (for documentation), and the main exploit script (poc.py). The exploit is a proof-of-concept and not weaponized for automated attacks.
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.