Loading vulnerability…
A stack-based buffer overflow exists in GCoreServer.exe, part of the Geutebrueck Gcore server (versions 1.3.8.42 and 1.4.2.37). The vulnerability is triggered by sending a specially crafted GET request with an excessively long URI, which overflows a stack buffer and allows for 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 (1 hidden).
This repository contains a single Metasploit module (Ruby file) that exploits a stack buffer overflow vulnerability (CVE-2017-11517) in Geutebrueck GCoreServer.exe, a component of the Geutebrueck GCore video surveillance system. The exploit targets Windows x64 systems running vulnerable versions of GCoreServer.exe (from 2003 up to July 2016, specifically 1.3.8.42 and 1.4.2.37) on TCP ports 13003 or 13004. No authentication is required. The module first fingerprints the target by requesting the '/statistics/runningmoduleslist.xml' endpoint to determine the server version. If a vulnerable version is detected, it crafts a malicious HTTP GET request that triggers a buffer overflow, allowing the attacker to execute arbitrary code with high privileges. The payload is customizable via Metasploit and typically results in a reverse shell or similar remote access. The exploit is operational and can be used to gain full control over affected systems. The repository is structured as a single Ruby file compatible with the Metasploit framework.
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.