dbcve.org
Sma1000 FirmwareOperating system · Sonicwall

CVE-2025-2170

HIGH · 7.2 CVSS v3.1 Published 2025-04-30
Fix available
A fix is available. Upgrade to 12.4.3-02925 or later.
See remediation →
81/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
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.

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

A Server-side Request Forgery (SSRF) vulnerability exists in the SMA1000 Appliance Work Place interface that allows remote unauthenticated attackers to force the appliance to make HTTP requests to attacker-controlled or internal locations, potentially enabling internal network reconnaissance or pivoting to internal services.

MitigationRestrict network access to the SMA1000 Work Place interface to trusted IPs, implement strict allow-list validation for any URL/path parameters, and apply vendor patches when released.

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
Sma1000 FirmwareOperating system
Affected:< 12.4.3-02925

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/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 the installed SMA100 firmware version
    Access the SMA100 administrative interface or check via CLI using 'get system status' or similar version command. Look for a build/revision number in the format 12.4.x-XXXXX.
    Affected if The firmware version is below 12.4.3-02925 (for example, 12.4.2-02900 or earlier).
  2. Confirm the Work Place interface is enabled
    In the SMA100 web UI, navigate to the Work Place settings or check via CLI for Work Place module status. Look for any configuration that enables or exposes the Work Place portal functionality.
    Affected if The Work Place interface is enabled and accessible, as this is the attack surface for the SSRF vulnerability.
  3. Assess network accessibility of the Work Place interface
    Determine if the Work Place interface is reachable from untrusted networks. This may involve checking firewall rules, interface bindings, or whether the portal is exposed to the internet or untrusted LAN segments.
    Affected if The Work Place interface is reachable from unauthenticated/untrusted network locations, allowing remote attackers to trigger the SSRF.

A user is affected if their SMA100 firmware version is below 12.4.3-02925 AND the Work Place interface is enabled and accessible from untrusted networks.

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 12.4.3-02925 or later
Fixed in 12.4.3-02925
Interim mitigation

Restrict network access to the SMA1000 Work Place interface to trusted IPs, implement strict allow-list validation for any URL/path parameters, and apply vendor patches when released.

Recommended fix Moderate confidence

12.4.3-02925 or later

  1. 1. Log into the SMA1000 Appliance admin interface
  2. 2. Navigate to the firmware management or system settings section
  3. 3. Download the latest firmware version 12.4.3-02925 or later from the official SonicWall support portal
  4. 4. Backup the current appliance configuration
  5. 5. Upload and apply the firmware update following SonicWall's standard upgrade procedure
  6. 6. Verify the upgrade was successful by checking the firmware version in the admin interface
  7. 7. Confirm the Work Place interface functionality is operational
Caveat Review SonicWall release notes for any configuration changes or compatibility considerations before upgrading

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

Fix this in Sma1000 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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