Loading vulnerability…
A buffer overflow vulnerability exists in the os.symlink() function in CPython versions 3.2 through 3.6.4 on Windows. The vulnerability is triggered when a Python script creates a symbolic link with an attacker-controlled name or location, leading to a buffer overflow condition. This can allow an attacker to execute arbitrary code, potentially with escalated privileges.
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 contains a proof-of-concept exploit for CVE-2018-1000117, a buffer overflow vulnerability in the os.symlink() function of CPython on Windows (versions 2.7, 3.4, 3.5, and 3.6 up to 3.6.4). The exploit is implemented in a single Python script (p0c.py), which calls os.symlink() with overlong byte string arguments to trigger the overflow. The README.md provides background, affected versions, and credits. The exploit demonstrates the vulnerability but does not include a weaponized payload; it is intended for local execution on a vulnerable Windows system to show the flaw's existence. No network endpoints are present; the attack vector is local, requiring code execution privileges on the target machine.
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.