CVE-2022-22281
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 · uneditedA buffer overflow vulnerability in the SonicWall SSL-VPN NetExtender Windows Client (32 and 64 bit) in 10.2.322 and earlier versions, allows an attacker to potentially execute arbitrary code in the host windows operating system.
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 confidenceA buffer overflow vulnerability exists in the SonicWall SSL-VPN NetExtender Windows Client (both 32-bit and 64-bit versions) through version 10.2.322. The vulnerability allows an attacker to potentially execute arbitrary code on the target Windows host operating system.
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<= 10.2.322CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify if NetExtender is installedOpen Windows Settings > Apps > Apps & Features, or use PowerShell: Get-ItemProperty 'HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*' | Where-Object {$_.DisplayName -like '*NetExtender*'}. Also check Program Files for NetExtender folders.Affected if NetExtender is not found on the system, then not affected by this specific vulnerability.
-
Determine the installed NetExtender versionIf installed, locate the version by right-clicking the NetExtender executable in Program Files (typically in SonicWall\NetExtender or similar), selecting Properties, and checking the Details tab for File Version. Alternatively, launch NetExtender and look in the About or Help section.Affected if The displayed version is 10.2.322 or lower.
-
Verify exact version number against affected rangeCompare the found version number to the affected range: versions <= 10.2.322 are vulnerable. Note that the version format may appear as 10.2.322.x - any build at or below 10.2.322 is within the affected range.Affected if Version is 10.2.322 or any version number lower than 10.2.322.
-
Confirm NetExtender client is enabled or configuredCheck if NetExtender is configured as a VPN connection on the Windows machine. Look for NetExtender profiles in Windows VPN settings, or check if the NetExtender service is present in Services.msc and set to run.Affected if NetExtender is installed and configured as an available VPN connection on the system.
A user is affected if SonicWall NetExtender is installed on their Windows system with a version number at or below 10.2.322.
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.
dbcve · scopedUpgrade the SonicWall NetExtender Windows Client to a version newer than 10.2.322 that contains the security patch. Until patched, limit exposure by ensuring only trusted users connect to the VPN and by keeping endpoint protections enabled.
NetExtender 10.2.331 or later
- 1. Open the SonicWall NetExtender client or navigate to the SonicWall support site.
- 2. Download the latest version of NetExtender Windows Client (version 10.2.331 or later).
- 3. Uninstall the current NetExtender client from the Windows system via Control Panel > Programs and Features.
- 4. Install the newly downloaded NetExtender client version.
- 5. Restart the Windows system if prompted.
- 6. Verify the installed version matches the fixed release (10.2.331 or later) by checking Help > About in the NetExtender client.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-22281 — 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-2022-22281 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