CVE-2020-37075
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedLanSend 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceLanSend 3.2 contains a buffer overflow in the Add Computers Wizard file import functionality where parsing a maliciously crafted file allows overwriting the Structured Exception Handler (SEH), enabling arbitrary shellcode execution and remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify LanSend installation and versionLocate LanSend installation directory and check version information (typically via executable properties, installer records, or program's About/Help section)Affected if Installed version is LanSend 3.2 specifically
-
Verify Add Computers Wizard accessibilityLaunch LanSend and navigate to Add Computers Wizard feature to confirm it is present and accessible in the installed versionAffected if Add Computers Wizard feature exists and is accessible in the interface
-
Check for recent file import activityReview system logs, application logs, or recent file access timestamps for any .txt, .csv, or other import files used with the Add Computers WizardAffected if Any computer list files have been imported through the wizard, especially from untrusted sources
-
Inspect imported computer list filesExamine any imported files in the LanSend data directory or user documents for suspicious content, unusual file sizes, or malformed data that could indicate a crafted payloadAffected if Imported files show signs of tampering, unusual size, or contain unexpected binary data patterns
A user is affected if LanSend version 3.2 is installed AND the Add Computers Wizard file import feature has been used with potentially untrusted computer list files.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataDisable or restrict the file import feature until a patched version is available; never import computer lists from untrusted or unknown sources.
- Consultation4.0 h
- Implementation20.0 h
- Testing12.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-37075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-37075 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data