CVE-2020-37074
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 · uneditedRemote Desktop Audit 2.3.0.157 contains a buffer overflow vulnerability that allows attackers to execute arbitrary code during the Add Computers Wizard file import process. Attackers can craft a malicious payload file to trigger a structured exception handler (SEH) bypass and execute shellcode when importing computer lists.
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 confidenceBuffer overflow vulnerability in Remote Desktop Audit 2.3.0.157's Add Computers Wizard file import function allows attackers to execute arbitrary code via a crafted malicious payload file. The exploit leverages an SEH (Structured Exception Handler) bypass technique to execute shellcode during the computer list import process.
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.
-
Locate the SoftPerfect Remote Desktop Audit installationSearch for 'RDAudit.exe' or 'Remote Desktop Audit' in Program Files directories, or check the Windows installed programs list via Control Panel or 'Get-ItemProperty' in PowerShell for software named 'SoftPerfect Remote Desktop Audit'Affected if The software is installed on the system
-
Identify the installed versionRight-click the executable (typically in Program Files or Program Files (x86)), select Properties, and view the File Version on the Details tab. Alternatively, run 'Get-ItemProperty' on the .exe to retrieve the version infoAffected if The version is 2.3.0.157 (the specific affected version)
-
Confirm the Add Computers Wizard file import feature existsLaunch Remote Desktop Audit and navigate to the Add Computers Wizard function, typically found in the File menu or toolbar as an import option for computer listsAffected if The file import function is accessible and the feature is present in this version
-
Audit recent computer list importsCheck the application logs, recent file history, or the directory where imported computer list files are stored (commonly the user's Documents or application data folder) for recently imported .txt, .csv, or .rda filesAffected if Any computer list files were imported from untrusted or unverified sources since the vulnerable version is in use
A user is affected if SoftPerfect Remote Desktop Audit version 2.3.0.157 is installed and the Add Computers Wizard file import feature was used to load a computer list from an untrusted source.
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 dataAvoid importing computer lists from untrusted or unverified sources until an official vendor patch is released. Contact the vendor (SoftPerfect) for remediation and apply any available updates.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-37074 — 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-37074 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