CVE•Published 2022-11-15•Modified 2026-08-11•0 articles on news•5 live references•NVD data

CVE-2022-20922Cisco · Secure_firewall_threat_defense

Vulnerability data via NVD (ingested)

CVSS v3.1
5.8
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L
EPSS percentile
52
Exploit Prediction Scoring System · top 48% of all CVEs
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.

Timeline
Published 2022-11-15
Modified 2026-08-11

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common). Live host counts are a Premium feature.

More intel sources (5)

Known PoCs on GitHub

No public proof-of-concept repositories found for CVE-2022-20922 on GitHub.
We haven't classified any articles referencing CVE-2022-20922 yet. The external references above still apply.