# CVE-2025-2170: Server-side request forgery in SMA1000

> Remote unauthenticated attackers can exploit SSRF in the SMA1000 Work Place interface to force the appliance to make requests to unintended locations.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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:** 30 Apr 2025
- **Updated:** 14 May 2025
- **Also known as:** GHSA-66mc-jppc-fm4m

## What is CVE-2025-2170?

CVE-2025-2170 is a high-severity server-side request forgery vulnerability in SonicWall SMA1000, published on 30 Apr 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A Server-side request forgery (SSRF) vulnerability has been identified in the SMA1000 Appliance Work Place interface, which in specific conditions could potentially enable a remote unauthenticated attacker to cause the appliance to make requests to an unintended location.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-2170?

It affects 1 product.


Products: Sonicwall Sma1000 Firmware.

## How do I fix CVE-2025-2170?

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

## Is CVE-2025-2170 being exploited?

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

## Other vulnerabilities in SonicWall SMA1000

- [CVE-2023-0126](https://insights.sbomify.com/CVE-2023-0126/): Path traversal in SonicWall SMA1000 (high 7.5)
- [CVE-2020-5129](https://insights.sbomify.com/CVE-2020-5129/): Denial of service in SMA1000 (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2170 and fix it if it is affected.

What it is: CVE-2025-2170 is a high-severity server-side request forgery vulnerability in SonicWall SMA1000, published on 30 Apr 2025. 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-2025-2170 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-2025-2170/ (Markdown: https://insights.sbomify.com/CVE-2025-2170/index.md)
```

## Sources

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

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