9.8 CVE-2024-40766

CISA Kev Catalog Local Execution Code

An improper access control vulnerability has been identified in the SonicWall SonicOS management access, potentially leading to unauthorized resource access and in specific conditions, causing the firewall to crash. This issue affects SonicWall Firewall Gen 5 and Gen 6 devices, as well as Gen 7 devices running SonicOS 7.0.1-5035 and older versions.
https://nvd.nist.gov/vuln/detail/CVE-2024-40766

References

PSIRT@sonicwall.com

https://psirt.global.sonicwall.com/vuln-detail/SNWLID-2024-0015 Vendor Advisory

CPE

cpe	start	end
Configuration 1
AND
cpe:2.3:o:sonicwall:sonicos::::::::		< 5.9.2.14-13o
Running on/with
cpe:2.3:h:sonicwall:soho:-:::::::*
Configuration 2
AND
cpe:2.3:o:sonicwall:sonicos::::::::		< 6.5.2.8-2n
Running on/with
cpe:2.3:h:sonicwall:nssp_12400:-:::::::*
cpe:2.3:h:sonicwall:nssp_12800:-:::::::*
cpe:2.3:h:sonicwall:sm9800:-:::::::*
Configuration 3
AND
cpe:2.3:o:sonicwall:sonicos::::::::		< 6.5.4.15.116n
Running on/with
cpe:2.3:h:sonicwall:nsa_2650:-:::::::*
cpe:2.3:h:sonicwall:nsa_3600:-:::::::*
cpe:2.3:h:sonicwall:nsa_3650:-:::::::*
cpe:2.3:h:sonicwall:nsa_4600:-:::::::*
cpe:2.3:h:sonicwall:nsa_4650:-:::::::*
cpe:2.3:h:sonicwall:nsa_5600:-:::::::*
cpe:2.3:h:sonicwall:nsa_5650:-:::::::*
cpe:2.3:h:sonicwall:nsa_6600:-:::::::*
cpe:2.3:h:sonicwall:nsa_6650:-:::::::*
cpe:2.3:h:sonicwall:sm_9200:-:::::::*
cpe:2.3:h:sonicwall:sm_9250:-:::::::*
cpe:2.3:h:sonicwall:sm_9400:-:::::::*
cpe:2.3:h:sonicwall:sm_9450:-:::::::*
cpe:2.3:h:sonicwall:sm_9600:-:::::::*
cpe:2.3:h:sonicwall:sm_9650:-:::::::*
cpe:2.3:h:sonicwall:soho_250:-:::::::*
cpe:2.3:h:sonicwall:soho_250w:-:::::::*
cpe:2.3:h:sonicwall:sohow:-:::::::*
cpe:2.3:h:sonicwall:tz_300:-:::::::*
cpe:2.3:h:sonicwall:tz_300p:-:::::::*
cpe:2.3:h:sonicwall:tz_300w:-:::::::*
cpe:2.3:h:sonicwall:tz_350:-:::::::*
cpe:2.3:h:sonicwall:tz_350w:-:::::::*
cpe:2.3:h:sonicwall:tz_400:-:::::::*
cpe:2.3:h:sonicwall:tz_400w:-:::::::*
cpe:2.3:h:sonicwall:tz_500:-:::::::*
cpe:2.3:h:sonicwall:tz_500w:-:::::::*
cpe:2.3:h:sonicwall:tz_600:-:::::::*
cpe:2.3:h:sonicwall:tz_600p:-:::::::*
Configuration 4
AND
cpe:2.3:o:sonicwall:sonicos::::::::		<= 7.0.1-5035
Running on/with
cpe:2.3:h:sonicwall:nsa_2700:-:::::::*
cpe:2.3:h:sonicwall:nsa_3700:-:::::::*
cpe:2.3:h:sonicwall:nsa_4700:-:::::::*
cpe:2.3:h:sonicwall:nsa_5700:-:::::::*
cpe:2.3:h:sonicwall:nsa_6700:-:::::::*
cpe:2.3:h:sonicwall:nssp_10700:-:::::::*
cpe:2.3:h:sonicwall:nssp_11700:-:::::::*
cpe:2.3:h:sonicwall:nssp_13700:-:::::::*
cpe:2.3:h:sonicwall:tz270:-:::::::*
cpe:2.3:h:sonicwall:tz270w:-:::::::*
cpe:2.3:h:sonicwall:tz370:-:::::::*
cpe:2.3:h:sonicwall:tz370w:-:::::::*
cpe:2.3:h:sonicwall:tz470:-:::::::*
cpe:2.3:h:sonicwall:tz470w:-:::::::*
cpe:2.3:h:sonicwall:tz570:-:::::::*
cpe:2.3:h:sonicwall:tz570p:-:::::::*
cpe:2.3:h:sonicwall:tz570w:-:::::::*
cpe:2.3:h:sonicwall:tz670:-:::::::*

REMEDIATION

EXPLOITS

Exploit-db.com

id	description	date
No known exploits

POC Github

Url
No known exploits

Other Nist (github, ...)

Url
No known exploits

CAPEC

Common Attack Pattern Enumerations and Classifications

id	description	severity
19	Embedding Scripts within Scripts An adversary leverages the capability to execute their own script by embedding it within other scripts that the target software is likely to execute due to programs' vulnerabilities that are brought on by allowing remote hosts to execute scripts. [Spider] Using a browser or an automated tool, an adversary records all entry points for inputs that happen to be reflected in a client-side script element. These script elements can be located in the HTML content (head, body, comments), in an HTML tag, XML, CSS, etc. [Probe identified potential entry points for XSS vulnerability] The adversary uses the entry points gathered in the "Explore" phase as a target list and injects various common script payloads to determine if an entry point actually represents a vulnerability and to characterize the extent to which the vulnerability can be exploited. [Steal session IDs, credentials, page content, etc.] As the adversary succeeds in exploiting the vulnerability, they can choose to steal user's credentials in order to reuse or to analyze them later on. [Forceful browsing] When the adversary targets the current application or another one (through CSRF vulnerabilities), the user will then be the one who perform the attacks without being aware of it. These attacks are mostly targeting application logic flaws, but it can also be used to create a widespread attack against a particular website on the user's current network (Internet or not). [Content spoofing] By manipulating the content, the adversary targets the information that the user would like to get from the website.	High
441	Malicious Logic Insertion An adversary installs or adds malicious logic (also known as malware) into a seemingly benign component of a fielded system. This logic is often hidden from the user of the system and works behind the scenes to achieve negative impacts. With the proliferation of mass digital storage and inexpensive multimedia devices, Bluetooth and 802.11 support, new attack vectors for spreading malware are emerging for things we once thought of as innocuous greeting cards, picture frames, or digital projectors. This pattern of attack focuses on systems already fielded and used in operation as opposed to systems and their components that are still under development and part of the supply chain.	High
478	Modification of Windows Service Configuration An adversary exploits a weakness in access control to modify the execution parameters of a Windows service. The goal of this attack is to execute a malicious binary in place of an existing service. [Determine target system] The adversary must first determine the system they wish to modify the registry of. This needs to be a windows machine as this attack only works on the windows registry. [Gain access to the system] The adversary needs to gain access to the system in some way so that they can modify the windows registry. [Modify windows registry] The adversary will modify the windows registry by changing the configuration settings for a service. Specifically, the adversary will change the path settings to define a path to a malicious binary to be executed.	High
479	Malicious Root Certificate An adversary exploits a weakness in authorization and installs a new root certificate on a compromised system. Certificates are commonly used for establishing secure TLS/SSL communications within a web browser. When a user attempts to browse a website that presents a certificate that is not trusted an error message will be displayed to warn the user of the security risk. Depending on the security settings, the browser may not allow the user to establish a connection to the website. Adversaries have used this technique to avoid security warnings prompting users when compromised systems connect over HTTPS to adversary controlled web servers that spoof legitimate websites in order to collect login credentials.	Low
502	Intent Spoof An adversary, through a previously installed malicious application, issues an intent directed toward a specific trusted application's component in an attempt to achieve a variety of different objectives including modification of data, information disclosure, and data injection. Components that have been unintentionally exported and made public are subject to this type of an attack. If the component trusts the intent's action without verififcation, then the target application performs the functionality at the adversary's request, helping the adversary achieve the desired negative technical impact.
503	WebView Exposure An adversary, through a malicious web page, accesses application specific functionality by leveraging interfaces registered through WebView's addJavascriptInterface API. Once an interface is registered to WebView through addJavascriptInterface, it becomes global and all pages loaded in the WebView can call this interface.
536	Data Injected During Configuration An attacker with access to data files and processes on a victim's system injects malicious data into critical operational data during configuration or recalibration, causing the victim's system to perform in a suboptimal manner that benefits the adversary. [Determine configuration process] The adversary, through a previously compromised system, either remotely or physically, determines what the configuration process is. They look at configuration files, data files, and running processes on the system to identify areas where they could inject malicious data. [Determine when configuration occurs] The adversary needs to then determine when configuration or recalibration of a system occurs so they know when to inject malicious data. [Determine malicious data to inject] By looking at the configuration process, the adversary needs to determine what malicious data they want to insert and where to insert it. [Inject malicious data] Right before, or during system configuration, the adversary injects the malicious data. This leads to the system behaving in a way that is beneficial to the adversary and is often followed by other attacks.	High
546	Incomplete Data Deletion in a Multi-Tenant Environment An adversary obtains unauthorized information due to insecure or incomplete data deletion in a multi-tenant environment. If a cloud provider fails to completely delete storage and data from former cloud tenants' systems/resources, once these resources are allocated to new, potentially malicious tenants, the latter can probe the provided resources for sensitive information still there.	Medium
550	Install New Service When an operating system starts, it also starts programs called services or daemons. Adversaries may install a new service which will be executed at startup (on a Windows system, by modifying the registry). The service name may be disguised by using a name from a related operating system or benign software. Services are usually run with elevated privileges.
551	Modify Existing Service When an operating system starts, it also starts programs called services or daemons. Modifying existing services may break existing services or may enable services that are disabled/not commonly used.
552	Install Rootkit An adversary exploits a weakness in authentication to install malware that alters the functionality and information provide by targeted operating system API calls. Often referred to as rootkits, it is often used to hide the presence of programs, files, network connections, services, drivers, and other system components.	High
556	Replace File Extension Handlers When a file is opened, its file handler is checked to determine which program opens the file. File handlers are configuration properties of many operating systems. Applications can modify the file handler for a given file extension to call an arbitrary program when a file with the given extension is opened.
558	Replace Trusted Executable An adversary exploits weaknesses in privilege management or access control to replace a trusted executable with a malicious version and enable the execution of malware when that trusted executable is called.	High
562	Modify Shared File An adversary manipulates the files in a shared location by adding malicious programs, scripts, or exploit code to valid content. Once a user opens the shared content, the tainted content is executed.
563	Add Malicious File to Shared Webroot An adversaries may add malicious content to a website through the open file share and then browse to that content with a web browser to cause the server to execute the content. The malicious content will typically run under the context and permissions of the web server process, often resulting in local system or administrative privileges depending on how the web server is configured.
564	Run Software at Logon Operating system allows logon scripts to be run whenever a specific user or users logon to a system. If adversaries can access these scripts, they may insert additional code into the logon script. This code can allow them to maintain persistence or move laterally within an enclave because it is executed every time the affected user or users logon to a computer. Modifying logon scripts can effectively bypass workstation and enclave firewalls. Depending on the access configuration of the logon scripts, either local credentials or a remote administrative account may be necessary.
578	Disable Security Software An adversary exploits a weakness in access control to disable security tools so that detection does not occur. This can take the form of killing processes, deleting registry keys so that tools do not start at run time, deleting log files, or other methods.	Medium

MITRE

Techniques

id	description
T1014	Rootkit
T1027.009	Obfuscated Files or Information: Embedded Payloads
T1037	Boot or Logon Initialization Scripts
T1080	Taint shared content
T1505.005	Server Software Component: Terminal Services DLL
T1542.003	Pre-OS Boot:Bootkit
T1543	Create or Modify System Process
T1543.001	Create or Modify System Process: Launch Agent
T1543.003	Create or Modify System Process:Windows Service
T1543.004	Create or Modify System Process: Launch Daemon
T1546.001	Event Triggered Execution:Change Default File Association
T1546.004	Event Triggered Execution:.bash_profile and .bashrc
T1546.008	Event Triggered Execution: Accessibility Features
T1546.016	Event Triggered Execution: Installer Packages
T1547	Boot or Logon Autostart Execution
T1547.006	Boot or Logon Autostart Execution:Kernel Modules and Extensions
T1553.004	Subvert Trust Controls:Install Root Certificate
T1556.006	Modify Authentication Process: Multi-Factor Authentication
T1562.001	Impair Defenses: Disable or Modify Tools
T1562.002	Impair Defenses: Disable Windows Event Logging
T1562.004	Impair Defenses: Disable or Modify System Firewall
T1562.007	Impair Defenses: Disable or Modify Cloud Firewall
T1562.008	Impair Defenses: Disable Cloud Logs
T1562.009	Impair Defenses: Safe Mode Boot
T1574.011	Hijack Execution Flow:Service Registry Permissions Weakness
© 2022 The MITRE Corporation. This work is reproduced and distributed with the permission of The MITRE Corporation.

Mitigations

id	description
T1027.009	On Windows 10, enable Attack Surface Reduction (ASR) rules to prevent execution of potentially obfuscated scripts.
T1037	Ensure proper permissions are set for Registry hives to prevent users from modifying keys for logon scripts that may lead to persistence.
T1080	Protect shared folders by minimizing users who have write access.
T1505.005	Consider using Group Policy to configure and block modifications to Terminal Services parameters in the Registry.
T1542.003	Ensure proper permissions are in place to help prevent adversary access to privileged accounts necessary to install a bootkit.
T1543	Limit privileges of user accounts and groups so that only authorized administrators can interact with system-level process changes and service configurations.
T1543.001	Set group policies to restrict file permissions to the <code>~/launchagents</code> folder.
T1543.003	Limit privileges of user accounts and groups so that only authorized administrators can interact with service changes and service configurations.
T1543.004	Limit privileges of user accounts and remediate Privilege Escalation vectors so only authorized administrators can create new Launch Daemons.
T1546.004	Making these files immutable and only changeable by certain administrators will limit the ability for adversaries to easily create user level persistence.
T1546.008	To use this technique remotely, an adversary must use it in conjunction with RDP. Ensure that Network Level Authentication is enabled to force the remote desktop session to authenticate before the session is created and the login screen displayed. It is enabled by default on Windows Vista and later.
T1547.006	Use MDM to disable user's ability to install or approve kernel extensions, and ensure all approved kernel extensions are in alignment with policies specified in <code>com.apple.syspolicy.kernel-extension-policy</code>.
T1553.004	HTTP Public Key Pinning (HPKP) is one method to mitigate potential Adversary-in-the-Middle situations where and adversary uses a mis-issued or fraudulent certificate to intercept encrypted communications by enforcing use of an expected certificate.
T1556.006	Ensure that proper policies are implemented to dictate the secure enrollment and deactivation of MFA for user accounts.
T1562.001	Ensure proper user permissions are in place to prevent adversaries from disabling or interfering with security services.
T1562.002	Ensure proper user permissions are in place to prevent adversaries from disabling or interfering with logging.
T1562.004	Ensure proper user permissions are in place to prevent adversaries from disabling or modifying firewall settings.
T1562.007	Ensure least privilege principles are applied to Identity and Access Management (IAM) security policies.
T1562.008	Configure default account policy to enable logging. Manage policies to ensure only necessary users have permissions to make changes to logging policies.
T1562.009	Ensure that endpoint defenses run in safe mode.
T1574.011	Ensure proper permissions are set for Registry hives to prevent users from modifying keys for system components that may lead to privilege escalation.
© 2022 The MITRE Corporation. Esta obra se reproduce y distribuye con el permiso de The MITRE Corporation.

Cybersecurity needs ?

Strengthen software security from the outset with our DevSecOps expertise

Integrate security right from the start of the software development cycle for more robust applications and greater customer confidence.
Our team of DevSecOps experts can help you secure your APIs, data pipelines, CI/CD chains, Docker containers and Kubernetes deployments.

Discover this offer

Soutenez No Hack Me sur Tipeee

cpe	start	end
Configuration 1
AND
cpe:2.3:o:sonicwall:sonicos::::::::		< 5.9.2.14-13o
Running on/with
cpe:2.3:h:sonicwall:soho:-:::::::*
Configuration 2
AND
cpe:2.3:o:sonicwall:sonicos::::::::		< 6.5.2.8-2n
Running on/with
cpe:2.3:h:sonicwall:nssp_12400:-:::::::*
cpe:2.3:h:sonicwall:nssp_12800:-:::::::*
cpe:2.3:h:sonicwall:sm9800:-:::::::*
Configuration 3
AND
cpe:2.3:o:sonicwall:sonicos::::::::		< 6.5.4.15.116n
Running on/with
cpe:2.3:h:sonicwall:nsa_2650:-:::::::*
cpe:2.3:h:sonicwall:nsa_3600:-:::::::*
cpe:2.3:h:sonicwall:nsa_3650:-:::::::*
cpe:2.3:h:sonicwall:nsa_4600:-:::::::*
cpe:2.3:h:sonicwall:nsa_4650:-:::::::*
cpe:2.3:h:sonicwall:nsa_5600:-:::::::*
cpe:2.3:h:sonicwall:nsa_5650:-:::::::*
cpe:2.3:h:sonicwall:nsa_6600:-:::::::*
cpe:2.3:h:sonicwall:nsa_6650:-:::::::*
cpe:2.3:h:sonicwall:sm_9200:-:::::::*
cpe:2.3:h:sonicwall:sm_9250:-:::::::*
cpe:2.3:h:sonicwall:sm_9400:-:::::::*
cpe:2.3:h:sonicwall:sm_9450:-:::::::*
cpe:2.3:h:sonicwall:sm_9600:-:::::::*
cpe:2.3:h:sonicwall:sm_9650:-:::::::*
cpe:2.3:h:sonicwall:soho_250:-:::::::*
cpe:2.3:h:sonicwall:soho_250w:-:::::::*
cpe:2.3:h:sonicwall:sohow:-:::::::*
cpe:2.3:h:sonicwall:tz_300:-:::::::*
cpe:2.3:h:sonicwall:tz_300p:-:::::::*
cpe:2.3:h:sonicwall:tz_300w:-:::::::*
cpe:2.3:h:sonicwall:tz_350:-:::::::*
cpe:2.3:h:sonicwall:tz_350w:-:::::::*
cpe:2.3:h:sonicwall:tz_400:-:::::::*
cpe:2.3:h:sonicwall:tz_400w:-:::::::*
cpe:2.3:h:sonicwall:tz_500:-:::::::*
cpe:2.3:h:sonicwall:tz_500w:-:::::::*
cpe:2.3:h:sonicwall:tz_600:-:::::::*
cpe:2.3:h:sonicwall:tz_600p:-:::::::*
Configuration 4
AND
cpe:2.3:o:sonicwall:sonicos::::::::		<= 7.0.1-5035
Running on/with
cpe:2.3:h:sonicwall:nsa_2700:-:::::::*
cpe:2.3:h:sonicwall:nsa_3700:-:::::::*
cpe:2.3:h:sonicwall:nsa_4700:-:::::::*
cpe:2.3:h:sonicwall:nsa_5700:-:::::::*
cpe:2.3:h:sonicwall:nsa_6700:-:::::::*
cpe:2.3:h:sonicwall:nssp_10700:-:::::::*
cpe:2.3:h:sonicwall:nssp_11700:-:::::::*
cpe:2.3:h:sonicwall:nssp_13700:-:::::::*
cpe:2.3:h:sonicwall:tz270:-:::::::*
cpe:2.3:h:sonicwall:tz270w:-:::::::*
cpe:2.3:h:sonicwall:tz370:-:::::::*
cpe:2.3:h:sonicwall:tz370w:-:::::::*
cpe:2.3:h:sonicwall:tz470:-:::::::*
cpe:2.3:h:sonicwall:tz470w:-:::::::*
cpe:2.3:h:sonicwall:tz570:-:::::::*
cpe:2.3:h:sonicwall:tz570p:-:::::::*
cpe:2.3:h:sonicwall:tz570w:-:::::::*
cpe:2.3:h:sonicwall:tz670:-:::::::*