LiveActive security incident?Get immediate response
CVE Record

CVE-2020-37075: LanSend 3.2 - Buffer Overflow (SEH)

LanSend 3.2 contains a buffer overflow vulnerability in the Add Computers Wizard file import functionality that allows remote attackers to execute arbitrary code. Attackers can craft a malicious payload file to trigger a structured exception handler (SEH) overwrite and execute shellcode when importing computers from a file.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

LanSend 3.2 has a critical memory-corruption flaw in its computer-list import feature. A malicious import file can cause code execution in the context of the user running LanSend. Public exploit material exists, but the provided sources do not show active exploitation or CISA KEV listing.

Executive priority

Treat as high-priority if LanSend 3.2 is present. The business risk is arbitrary code execution through a legacy administrative utility with public exploit details. Prioritize inventory, removal or upgrade decisions, and controls around untrusted import files.

Technical view

CVE-2020-37075 is a CWE-120 buffer overflow in LizardSystems LanSend 3.2 Add Computers Wizard file import handling. The advisory describes an SEH overwrite leading to arbitrary code execution. The CVSS v3.1 score is 9.8, though the description indicates exploitation involves a crafted file being imported.

Likely exposure

Organizations are exposed if they still run LizardSystems LanSend 3.2, especially where users import computer lists from untrusted or externally supplied files. Exposure is likely limited to endpoints or administrative workstations where LanSend is installed.

Exploitation context

ExploitDB and VulnCheck reference public exploit information. The provided data does not establish active exploitation in the wild. Practical exploitation appears tied to processing a malicious import file in LanSend’s Add Computers Wizard.

Researcher notes

The CVSS vector lists UI:N, but the narrative centers on importing a crafted file. Validate exploitability assumptions against the original advisory before modeling remote exposure. No patch status is provided in the source bundle, so remediation should be grounded in vendor guidance or decommissioning.

Mitigation direction

  • Identify and inventory any LanSend 3.2 installations.
  • Check LizardSystems guidance for supported versions, fixes, or upgrade paths.
  • Avoid importing computer lists from untrusted sources.
  • Restrict LanSend use to trusted administrative workstations.
  • Remove LanSend where it is not business-critical.

Validation and detection

  • Search software inventory for LizardSystems LanSend version 3.2.
  • Confirm whether users import computer lists from files.
  • Review endpoint controls for LanSend execution and file handling.
  • Check vendor and advisory pages for updated remediation information.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-120: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-37075 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-37075Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
LizardSystemsLanSend3.2Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-120 · source CWE mapping

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow')

Buffer Copy without Checking Size of Input ('Classic Buffer Overflow') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.