Capture ClientApplication · Sonicwall

CVE-2023-6340

MEDIUM · 5.5 CVSS v3.1 Published 2024-01-18
Fix available
A fix is available. Upgrade to after 10.2.337 or later.
See remediation →
57/100
Remediation priority · Elevated
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 Capture Client version 3.7.10, NetExtender client version 10.2.337 and earlier versions are installed with sfpmonitor.sys driver. The driver has been found to be vulnerable to Denial-of-Service (DoS) caused by Stack-based Buffer Overflow vulnerability.

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 · moderate confidence

The sfpmonitor.sys kernel driver in SonicWall Capture Client 3.7.10 and NetExtender client version 10.2.337 and earlier contains a stack-based buffer overflow vulnerability that can be exploited to cause a denial of service. The vulnerability is triggered when the driver processes malformed input, leading to stack memory corruption and system crash.

MitigationApply vendor-supplied patches or updates to SonicWall Capture Client and NetExtender to obtain patched versions of the sfpmonitor.sys driver. If updates are unavailable, consider disabling the affected service or implementing network-based controls to limit exposure to adjacent attackers.

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
Capture ClientApplication
Affected:<= 3.7.10
NetextenderApplication
Affected:<= 10.2.337

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:N/I:N/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. Identify if SonicWall Capture Client is installed
    Check the installed programs list or look for the application in Program Files. Verify the version by checking the executable properties or using 'Get-ItemProperty' in PowerShell for HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* or checking the application directory for version info.
    Affected if The installed version is 3.7.10 or lower.
  2. Identify if SonicWall NetExtender is installed
    Check the installed programs list or look for NetExtender in Program Files. Verify the version by checking the executable properties or registry keys under HKLM:\SOFTWARE\SonicWall\NetExtender or HKCU:\SOFTWARE\SonicWall\NetExtender.
    Affected if The installed version is 10.2.337 or lower.
  3. Locate the sfpmonitor.sys driver file
    Search for sfpmonitor.sys in the Windows\System32\drivers directory or within the SonicWall application installation folders. Use 'Get-ChildItem -Path C:\ -Filter sfpmonitor.sys -Recurse -ErrorAction SilentlyContinue' or check typical SonicWall install paths.
    Affected if The driver file exists on the system.
  4. Check the driver's file version
    Right-click the sfpmonitor.sys file, select Properties, and examine the File Version field. Alternatively, use PowerShell: (Get-Item 'C:\path\to\sfpmonitor.sys').VersionInfo.
    Affected if The file version corresponds to the affected product versions (Capture Client <= 3.7.10 or NetExtender <= 10.2.337).

The system is affected if either SonicWall Capture Client version 3.7.10 or lower, or SonicWall NetExtender version 10.2.337 or lower, is installed and the sfpmonitor.sys driver is present on the system.

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 10.2.337
Interim mitigation

Apply vendor-supplied patches or updates to SonicWall Capture Client and NetExtender to obtain patched versions of the sfpmonitor.sys driver. If updates are unavailable, consider disabling the affected service or implementing network-based controls to limit exposure to adjacent attackers.

Fix this in Capture Client Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-6340 — 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-2023-6340 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