Local code execution via scan buffer overflow
Published Apr 22, 2026 · Updated Apr 22, 2026
Buffer overflow in the scan section of LizardSystems LanSpy 2.0.1.159 allows local users to execute arbitrary code via crafted input. Oversized scan data corrupts the SEH chain, redirects a controlled jump to an egghunter, and locates attacker-supplied shellcode in memory. Local access to the application is required, and successful exploitation runs code in the security context of the LanSpy process.
Summary
What happened
Buffer overflow in the scan section of LizardSystems LanSpy 2.0.1.159 allows local users to execute arbitrary code via crafted input. Oversized scan data corrupts the SEH chain, redirects a controlled jump to an egghunter, and locates attacker-supplied shellcode in memory. Local access to the application is required, and successful exploitation runs code in the security context of the LanSpy process.
The record
- CVE
- CVE-2018-25265
- Published
- Apr 22, 2026
- Updated
- Apr 22, 2026
- Vendor
- LizardSystems
- Product
- LanSpy
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 22, 2026CVE publishedPublication date reported by the CVE source.
- Apr 22, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=2.0.1.159
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
- LanSpy 2.0.1.159 Local Buffer Overflowproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo