Code execution via unchecked import filename
Published Feb 3, 2026 · Updated Feb 3, 2026
Buffer overflow in LanSend 3.2 allows attackers to execute arbitrary code through a crafted filename in the Add Computers Wizard. The filename input is copied without a size check, overwriting the structured exception handler and redirecting execution to embedded shellcode. Exploitation requires a user to open the wizard and supply the payload as the import filename; code runs in the LanSend process context.
Summary
What happened
Buffer overflow in LanSend 3.2 allows attackers to execute arbitrary code through a crafted filename in the Add Computers Wizard. The filename input is copied without a size check, overwriting the structured exception handler and redirecting execution to embedded shellcode. Exploitation requires a user to open the wizard and supply the payload as the import filename; code runs in the LanSend process context.
The record
- CVE
- CVE-2020-37075
- Published
- Feb 3, 2026
- Updated
- Feb 3, 2026
- Vendor
- LizardSystems
- Product
- LanSend
- Classifications
- CWE-120, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 3, 2026CVE publishedPublication date reported by the CVE source.
- Feb 3, 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=3.2
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.
Weakness, pattern, technique
Public exploit references
- LanSend 3.2 Buffer Overflow SEH exploitfunctional · demonstrated
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