<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Lizardsystems — CraftedSignal Threat Feed</title><link>https://feed.craftedsignal.io/vendors/lizardsystems/</link><description>Trending threats, MITRE ATT&amp;CK coverage, and detection metadata — refreshed continuously.</description><generator>Hugo</generator><language>en</language><managingEditor>hello@craftedsignal.io</managingEditor><webMaster>hello@craftedsignal.io</webMaster><lastBuildDate>Wed, 22 Apr 2026 16:16:47 +0000</lastBuildDate><atom:link href="https://feed.craftedsignal.io/vendors/lizardsystems/feed.xml" rel="self" type="application/rss+xml"/><item><title>LanSpy 2.0.1.159 Local Buffer Overflow Vulnerability</title><link>https://feed.craftedsignal.io/briefs/2026-04-lanspy-buffer-overflow/</link><pubDate>Wed, 22 Apr 2026 16:16:47 +0000</pubDate><author>hello@craftedsignal.io</author><guid isPermaLink="true">https://feed.craftedsignal.io/briefs/2026-04-lanspy-buffer-overflow/</guid><description>LanSpy 2.0.1.159 is vulnerable to a local buffer overflow, allowing an attacker to overwrite the instruction pointer by providing a crafted payload to the scan field, potentially leading to code execution.</description><content:encoded><![CDATA[<p>LanSpy version 2.0.1.159 is susceptible to a local buffer overflow vulnerability (CVE-2018-25268). This vulnerability, reported in April 2026, stems from insufficient input validation within the application&rsquo;s scan field. An attacker, with local access to a vulnerable system, can exploit this flaw by crafting a specific payload designed to overwrite the instruction pointer. This can lead to application crashes or, more seriously, the potential execution of arbitrary code. The vulnerability exists because the application does not properly handle oversized input to the scan field.</p>
<h2 id="attack-chain">Attack Chain</h2>
<ol>
<li>Attacker gains local access to a system with LanSpy 2.0.1.159 installed.</li>
<li>The attacker crafts a malicious payload consisting of 688 bytes of padding.</li>
<li>The attacker appends 4 bytes of controlled data (representing the desired instruction pointer overwrite) to the padding.</li>
<li>The attacker inputs this crafted payload into the &ldquo;scan field&rdquo; of the LanSpy application.</li>
<li>Due to the buffer overflow vulnerability, the oversized input overwrites the application&rsquo;s buffer on the stack.</li>
<li>The 4 bytes of controlled data overwrite the instruction pointer (EIP on x86 architectures).</li>
<li>When the application attempts to return from the vulnerable function, it jumps to the address specified by the attacker-controlled instruction pointer.</li>
<li>This jump can lead to a crash or, if the attacker provides a valid address containing malicious code, code execution within the context of the LanSpy application.</li>
</ol>
<h2 id="impact">Impact</h2>
<p>Successful exploitation of this vulnerability allows an attacker to potentially execute arbitrary code on the affected system with the privileges of the user running LanSpy. While the exploit requires local access, it can be leveraged to escalate privileges or establish persistence on the compromised machine. There are no reliable victim counts or sectors targeted available.</p>
<h2 id="recommendation">Recommendation</h2>
<ul>
<li>Due to the age of this software and the lack of available patches, consider uninstalling LanSpy 2.0.1.159 from systems where it is present.</li>
<li>Monitor process execution for unexpected crashes of LanSpy using the <code>process_creation</code> log source to identify exploitation attempts.</li>
<li>Deploy the Sigma rule to detect potential buffer overflow exploitation attempts by monitoring for abnormally large inputs to the LanSpy process in <code>process_creation</code> logs.</li>
</ul>
]]></content:encoded><category domain="severity">high</category><category domain="type">advisory</category><category>buffer-overflow</category><category>code-execution</category><category>cve-2018-25268</category></item></channel></rss>