CVE-2022-20922
CVE-2022-20922
In short
Snort 3 security software on Cisco devices has a flaw in how it handles SMB2 network traffic. An attacker can send specially crafted packets to crash the security tool or bypass its protections.
Technical detail
The vulnerability exists in improper resource management within the SMB2 processor of Snort 3. An unauthenticated remote attacker can exploit this via high-rate SMB2 packet transmission, triggering process reload (DoS), or with preserve-connection enabled, bypassing configured policies to deliver malicious payloads to protected networks.
Summary generated and translated by AI from the official description.
Multiple vulnerabilities in the Server Message Block Version 2 (SMB2) processor of the Snort detection engine on multiple Cisco products could allow an unauthenticated, remote attacker to bypass the configured policies or cause a denial of service (DoS) condition on an affected device.
These vulnerabilities are due to improper management of system resources when the Snort detection engine is processing SMB2 traffic. An attacker could exploit these vulnerabilities by sending a high rate of certain types of SMB2 packets through an affected device. A successful exploit could allow the attacker to trigger a reload of the Snort process, resulting in a DoS condition.
Note: When the snort preserve-connection option is enabled for the Snort detection engine, a successful exploit could also allow the attacker to bypass the configured policies and deliver a malicious payload to the protected network. The snort preserve-connection setting is enabled by default. See the Details ["#details"] section of this advisory for more information.
Note: Only products that have Snort 3 configured are affected. Products that are configured with Snort 2 are not affected.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L
Affected products
Cisco · Cisco Cyber VisionCisco · Cisco Firepower Threat Defense SoftwareCisco · Cisco Umbrella Insights Virtual ApplianceWant to know if your infrastructure is exposed to this?
Talk to TrueHacking →