# CVE-2022-1701: Hardcoded credentials in SonicWall SMA1000

> Attackers can decrypt stored data using a hard-coded key, exposing sensitive information and bypassing security controls on SonicWall SMA1000 devices.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 May 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-rxgp-8c89-84pf

## What is CVE-2022-1701?

CVE-2022-1701 is a high-severity vulnerability in SonicWall SMA1000, published on 13 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-798 (Use of Hard-coded Credentials), CWE-321 (Use of Hard-coded Cryptographic Key)

## Which versions are affected by CVE-2022-1701?

It affects 5 products.


Products: Sonicwall Sma 6200 Firmware, Sonicwall Sma 6210 Firmware, Sonicwall Sma 7200 Firmware, Sonicwall Sma 7210 Firmware, Sonicwall Sma 8000v Firmware.

## How do I fix CVE-2022-1701?

No fix has been published for CVE-2022-1701 yet. Limit exposure of the affected software until one is available.

## Is CVE-2022-1701 being exploited?

There is no known exploitation of CVE-2022-1701 in the wild and no public exploit code.

## Other vulnerabilities in SonicWall SMA1000

- [CVE-2022-22282](https://insights.sbomify.com/CVE-2022-22282/): Missing authorization in SonicWall SMA1000 (critical 9.8)
- [CVE-2022-1702](https://insights.sbomify.com/CVE-2022-1702/): Open redirect in SonicWall SMA1000 (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-1701 and fix it if it is affected.

What it is: CVE-2022-1701 is a high-severity vulnerability in SonicWall SMA1000, published on 13 May 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-1701 in the wild and no public exploit code.

Affected product: SonicWall SMA1000. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-1701/ (Markdown: https://insights.sbomify.com/CVE-2022-1701/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-1701
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-1701
- OSV: https://osv.dev/vulnerability/CVE-2022-1701

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-1701/
Summaries are generated and may contain mistakes; the official description above is the record.