CVE-2025-40602: SonicWall SMA1000 Missing Authorization Vulnerability

What it is

A local privilege escalation vulnerability due to insufficient authorization in the SonicWall SMA1000 appliance management console (AMC).

Exploitation evidence

First exploit evidence seen: 2025-12-17 (earliest date across the sources below).

Exploited in the wild

• CISA KEV: listed since 2025-12-17. Source

Public exploit code

GitHub proof-of-concept repositories below quality bar

2 public repositories from 2 accounts, first seen 2025-12-18.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: CISA KEV · nomi-sec/PoC-in-GitHub.

How to fix it

CISA required action

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable (source: CISA KEV)

Fixed versions

• sonicwall sma6200 firmware: upgrade to 12.4.3-03245 or later
• sonicwall sma6200 firmware: upgrade to 12.5.0-02283 or later (affected from 12.5.0)
• sonicwall sma6210 firmware: upgrade to 12.4.3-03245 or later
• sonicwall sma6210 firmware: upgrade to 12.5.0-02283 or later (affected from 12.5.0)
• sonicwall sma7200 firmware: upgrade to 12.4.3-03245 or later
• sonicwall sma7200 firmware: upgrade to 12.5.0-02283 or later (affected from 12.5.0)
• sonicwall sma7210 firmware: upgrade to 12.4.3-03245 or later
• sonicwall sma7210 firmware: upgrade to 12.5.0-02283 or later (affected from 12.5.0)
• sonicwall sma8200v: upgrade to 12.4.3-03245 or later
• sonicwall sma8200v: upgrade to 12.5.0-02283 or later (affected from 12.5.0)

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2025-0019 (CISA KEV notes)

MITRE ATT&CK mitigations for this chain

• M1051 Update Software (for T1068) : Update software regularly by employing patch management for internal enterprise endpoints and servers.
• M1050 Exploit Protection (for T1068) : Security applications that look for behavior used during exploitation such as Windows Defender Exploit Guard (WDEG) and the Enhanced Mitigation Experience Toolkit (EMET) can be used to mitigate some exploitation behavior. Control flow integrity checking is another way to potentially identify and stop a software exploi
• M1048 Application Isolation and Sandboxing (for T1068) : Make it difficult for adversaries to advance their operation through exploitation of undiscovered or unpatched vulnerabilities by using sandboxing. Other types of virtualization and application microsegmentation may also mitigate the impact of some types of exploitation. Risks of additional exploits and weaknesses in t
• M1019 Threat Intelligence Program (for T1068) : Develop a robust cyber threat intelligence capability to determine what types and levels of threat may use software exploits and 0-days against a particular organization.
• M1038 Execution Prevention (for T1068) : Consider blocking the execution of known vulnerable drivers that adversaries may exploit to execute code in kernel mode. Validate driver block rules in audit mode to ensure stability prior to production deployment.

Detection Generic guidance

• Privilege Escalation: Alert on processes gaining SYSTEM/root unexpectedly, and on exploitation crashes of privileged services.

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.