Global Vpn ClientApplication · Sonicwall

CVE-2021-20037

HIGH · 7.8 CVSS v3.1 Published 2021-09-21
Fix available
A fix is available. Upgrade to after 4.10.5 or later.
See remediation →
80/100
Remediation priority · High
Zero-click

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 · unedited
SonicWall Global VPN Client 4.10.5 installer (32-bit and 64-bit) incorrect default file permission vulnerability leads to privilege escalation which potentially allows command execution in the host operating system. This vulnerability impacts GVC 4.10.5 installer and earlier.

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 confidence

SonicWall Global VPN Client 4.10.5 installer (32-bit and 64-bit) creates files with overly permissive default ACLs, allowing unprivileged local users to modify executable files or configurations. This incorrect file permission enables privilege escalation to execute commands with elevated SYSTEM privileges.

MitigationUpgrade to a patched version of SonicWall Global VPN Client (beyond 4.10.5) or apply vendor-provided security updates to remediate the improper file permissions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Global Vpn ClientApplication
Affected:<= 4.10.5

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if SonicWall Global VPN Client is installed
    Look for the application in the system registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or check for the presence of SonicWall client files in Program Files or Program Files (x86) directories
    Affected if The software is present on the system and was installed with version 4.10.5 or earlier
  2. Identify the installed version of SonicWall Global VPN Client
    Open the Windows Registry and navigate to HKLM\SOFTWARE\SonicWall\Global VPN Client\Version, or right-click the client executable and view its Properties to find the File Version
    Affected if The installed version is 4.10.5 or any version lower than 4.10.5
  3. Examine file permissions on the SonicWall installation directory
    Right-click the SonicWall Global VPN Client installation folder in Program Files, select Properties, go to the Security tab, and review the permissions for Users andAuthenticated Users groups
    Affected if Users or Authenticated Users have Write or Modify permissions to folders containing executable files (.exe) or configuration files (.xml, .ini, .conf)
  4. Verify executable files are modifiable by non-privileged users
    Open a command prompt as a standard (non-admin) user, navigate to the SonicWall installation directory, and attempt to delete or modify an executable file such as the client launcher or a .dll file
    Affected if Standard users can successfully modify, delete, or replace executable files in the SonicWall installation directory

A user is affected if SonicWall Global VPN Client version 4.10.5 or lower is installed and non-privileged users have write access to executable or configuration files in the installation directory.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 4.10.5
Interim mitigation

Upgrade to a patched version of SonicWall Global VPN Client (beyond 4.10.5) or apply vendor-provided security updates to remediate the improper file permissions.

Fix this in Global Vpn Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,744.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-20037 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-20037 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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