Loading vulnerability…
CVE-2015-1171 is a stack-based buffer overflow vulnerability in GSM SIM Utility (SIM Card Editor) version 6.6. The vulnerability is triggered when the application processes a .sms file containing an excessively long entry, leading to a buffer overflow on the stack. This can allow an attacker to overwrite critical stack data, including the return address, and potentially execute arbitrary code.
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 (modules/exploits/windows/fileformat/gsm_sim.rb) that exploits a stack-based buffer overflow vulnerability in GSM SIM Editor version 5.15 (CVE-2015-1171). The exploit works by generating a specially crafted .sms file, which, when opened by the victim in the vulnerable application on Windows XP SP3, triggers the overflow and allows execution of arbitrary code. The module allows the attacker to select a payload (up to 2000 bytes, with null byte filtering), which is embedded in the malicious file. The exploit is weaponized, as it is part of the Metasploit framework and supports customizable payloads. The main attack vector is local, requiring user interaction to open the malicious file. The only fingerprintable endpoint is the crafted .sms file itself. The repository is structured as a single Ruby file following Metasploit conventions, with all exploit logic contained within the file.
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.