dbcve.org
Sma 200 FirmwareOperating system · Sonicwall

CVE-2024-22395

MEDIUM · 6.3 CVSS v3.1 Published 2024-02-24
Fix available
A fix is available. Upgrade to 10.2.1.11-65sv or later.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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
Improper access control vulnerability has been identified in the SMA100 SSL-VPN virtual office portal, which in specific conditions could potentially enable a remote authenticated attacker to associate another user's MFA mobile application.

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

Improper access control in the SMA100 SSL-VPN virtual office portal allows an authenticated attacker to associate another user's MFA mobile application with their account, potentially enabling session hijacking or unauthorized VPN access through mismatched MFA credentials.

MitigationApply the vendor-supplied patch or firmware update for SMA100 series devices to enforce proper authorization checks when configuring MFA associations, preventing users from modifying other users' MFA settings.

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
Sma 200 FirmwareOperating system
Affected:< 10.2.1.11-65sv
Sma 210 FirmwareOperating system
Affected:< 10.2.1.11-65sv
Sma 400 FirmwareOperating system
Affected:< 10.2.1.11-65sv
Sma 410 FirmwareOperating system
Affected:< 10.2.1.11-65sv
Sma 500v FirmwareOperating system
Affected:< 10.2.1.11-65sv

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

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 the SMA device model
    Access the SMA web management console or check the device label to determine if the model is SMA 200, SMA 210, SMA 400, SMA 410, or SMA 500v. This vulnerability only affects these specific models.
    Affected if The device is NOT one of these models: SMA 200, SMA 210, SMA 400, SMA 410, or SMA 500v.
  2. Check the installed firmware version
    Log into the SMA web interface and navigate to System > Status or use the CLI command 'fw ver' to retrieve the current firmware version. Compare it to the fixed version 10.2.1.11-65sv.
    Affected if The firmware version is lower than 10.2.1.11-65sv.
  3. Verify if MFA is configured on the device
    Log into the SMA web interface and navigate to Users > Settings or Authentication > Multi-Factor Authentication to check if any MFA methods (such as mobile app, SMS, or hardware token) have been enabled for user accounts.
    Affected if MFA is NOT enabled or configured for any users on the device.
  4. Confirm virtual office portal accessibility
    Attempt to access the SMA SSL-VPN virtual office portal URL (typically port 4433 or 443) to verify the web interface is reachable and functional.
    Affected if The virtual office portal is not accessible or not in use.

The device is affected if it is an SMA 200, 210, 400, 410, or 500v running firmware below 10.2.1.11-65sv with MFA configured and the virtual office portal enabled.

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.

dbcve · scoped
Upgrade available Upgrade to 10.2.1.11-65sv or later
Fixed in 10.2.1.11-65sv
Interim mitigation

Apply the vendor-supplied patch or firmware update for SMA100 series devices to enforce proper authorization checks when configuring MFA associations, preventing users from modifying other users' MFA settings.

Recommended fix High confidence

10.2.1.11-65sv or later

  1. 1. Identify the specific SMA device model (200, 210, 400, 410, or 500v) in your environment
  2. 2. Access the SMA device management interface or CLI
  3. 3. Navigate to the firmware update section
  4. 4. Download the firmware version 10.2.1.11-65sv or later from the official SonicWall support portal (support.sonicwall.com)
  5. 5. Upload and apply the firmware update to the SMA device
  6. 6. After upgrade, verify the device is operational and test MFA functionality
  7. 7. Confirm the running firmware version is 10.2.1.11-65sv or higher

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Sma 200 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-22395 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-22395 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