cve.bz

CVE-2022-20943 cisco: Heap Inspection

5.8 mediumEPSS 1.1%

Medium (5.8) in cisco. EPSS 1.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

5.8 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:L
EPSS
1.1% (unchanged from 1.1% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 66th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-244 Improper Clearing of Heap Memory Before Release (Heap Inspection)
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2022-20943 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-20943?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-20943?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2022-20943 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
cisco:secure_firewall_threat_defense7.0.0
cisco:secure_firewall_threat_defense7.0.0.1
cisco:secure_firewall_threat_defense7.0.1
cisco:secure_firewall_threat_defense7.0.1.1
cisco:cyber_vision3.0.0
cisco:cyber_vision3.0.1
cisco:cyber_vision3.0.2
cisco:cyber_vision3.0.3
cisco:cyber_vision3.0.5
cisco:cyber_vision3.0.6
cisco:cyber_vision3.1.0
cisco:cyber_vision3.1.1
cisco:cyber_vision3.1.2
cisco:cyber_vision3.2.0
cisco:cyber_vision3.2.1
cisco:cyber_vision3.2.2
cisco:cyber_vision3.2.3
cisco:cyber_vision3.2.4
cisco:cyber_vision4.0.0
cisco:cyber_vision4.0.1
cisco:cyber_vision4.0.2
cisco:cyber_vision4.0.3
cisco:cyber_vision4.1.0
cisco:cyber_vision4.1.1
cisco:meraki_mx_security_appliance_firmwarebefore 16.6.7
cisco:meraki_mx_security_appliance_firmwarefrom 17.0 before 17.11.1
cisco:meraki_mx_security_appliance_firmwarefrom 18.0 before 18.1.3

References

Check your stackJSON