Skip to content
Fencer Intel
critical 10.0

CVE-2015-1171 in the critical feed json

Stack-based buffer overflow in GSM SIM Utility (aka SIM Card Editor) 6.6 allows remote attackers to execute arbitrary code via a long entry…

published 11y ago modified 4mo ago also EUVD-2015-1313

cvss
10.0
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
62.7%
EPSS 62.7% chance of exploitation in 30 days, percentile 99.1%
public exploits
2
Metasploit and Exploit-DB

Summary

Stack-based buffer overflow in GSM SIM Utility (aka SIM Card Editor) 6.6 allows remote attackers to execute arbitrary code via a long entry in a .sms file.

Is CVE-2015-1171 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/windows/fileformat/gsm_sim)
  2. Published

Exploit prediction

62.66% chance of exploitation in the next 30 days, higher than 99.1% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/windows/fileformat/gsm_sim GSM SIM Editor 5.15 Buffer Overflow metasploit exploit, normal rank, 2010-07-07
  • EDB-35821 Sim Editor 6.6 - Local Stack Buffer Overflow local, 2015-01-16
  • osandamalith.wordpress.com https://osandamalith.wordpress.com/2015/01/16/sim-editor-stack-based-buffer-overflow/ referenced PoC, tagged "exploit" by a source, unverified
  • packetstormsecurity.com http://packetstormsecurity.com/files/129992/simeditor-overflow.txt referenced PoC, tagged "exploit" by a source, unverified
  • youtube.com https://www.youtube.com/watch?v=tljbFpYtDTk referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

Classification

Weakness
  • CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.