dbcve.org
Sma 6200 FirmwareOperating system · Sonicwall

CVE-2022-1701

HIGH · 7.5 CVSS v3.1 Published 2022-05-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 SMA1000 series firmware 12.4.0, 12.4.1-02965 and earlier versions uses a shared and hard-coded encryption key to store data.

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 SonicWall SMA1000 series firmware versions 12.4.0, 12.4.1-02965 and earlier use a hard-coded encryption key for data storage. An attacker with access to the stored encrypted data can decrypt it using this known key, compromising confidentiality of sensitive information.

MitigationApply the vendor-supplied firmware update to a version later than 12.4.1-02965. After patching, audit and re-encrypt any sensitive data that may have been stored using the compromised key.

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 6200 FirmwareOperating system
Affected:= 12.4.0= 12.4.1
Sma 6210 FirmwareOperating system
Affected:= 12.4.0= 12.4.1
Sma 7200 FirmwareOperating system
Affected:= 12.4.0= 12.4.1
Sma 7210 FirmwareOperating system
Affected:= 12.4.0= 12.4.1
Sma 8000v FirmwareOperating system
Affected:= 12.4.0= 12.4.1

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

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

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 your SMA appliance model
    Access the SMA web management console and locate the device model number in the dashboard or status page, or run the command 'get system info' via CLI
    Affected if The model is one of: SMA 6200, SMA 6210, SMA 7200, SMA 7210, or SMA 8000v
  2. Determine the installed firmware version
    In the SMA web UI, go to Device > Settings > Firmware or use the CLI command 'version' to display the running firmware version
    Affected if The firmware version is 12.4.0, 12.4.1, or any version up to and including 12.4.1-02965
  3. Check for encrypted data storage in use
    Review the SMA configuration for any enabled encryption features such as password vault, VPN credentials, or encrypted configuration backups. Look for settings under Device > Settings > Encryption or similar encryption-related panels
    Affected if The appliance is configured to store any sensitive data (passwords, certificates, VPN keys, backup files) using the built-in encryption functionality
  4. Verify if hardcoded key encryption is active
    Examine the appliance for evidence that the default hardcoded encryption key is being used rather than a customer-managed key. This may be indicated by the absence of custom key configuration in encryption-related settings
    Affected if Custom encryption key management is not configured and the default encryption settings are in use

You are affected if you own an SMA 6200/6210/7200/7210/8000v appliance running firmware 12.4.0 through 12.4.1-02965 and have sensitive data encrypted using the built-in encryption features.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware update to a version later than 12.4.1-02965. After patching, audit and re-encrypt any sensitive data that may have been stored using the compromised key.

Recommended fix Moderate confidence

Firmware 12.4.2 or later (contact SonicWall for exact fixed version)

  1. 1. Contact SMA 100 series appliance or access my.sonicwall.com to obtain the latest firmware version.
  2. 2. Review SonicWall release notes for version 12.4.2 or later to confirm the hard-coded key vulnerability (CVE-2022-1701) is addressed.
  3. 3. Download the appropriate firmware for your specific model (6200, 6210, 7200, 7210, or 8000v).
  4. 4. Back up the current appliance configuration via the web management interface (Administration > Backup/Restore).
  5. 5. Upload and install the new firmware through the web management interface (Administration > Firmware Update).
  6. 6. After reboot, verify the firmware version and restore configuration if needed.
  7. 7. Confirm the hard-coded encryption key has been replaced with dynamically generated keys.
Caveat Review release notes for any configuration or feature changes between 12.4.x versions before upgrading

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

Fix this in Sma 6200 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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