cve.bz

CVE-2022-20933 cisco: Failure to Handle Missing Parameter

8.6 highEPSS 1.1%

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

On this page
A vulnerability in the Cisco AnyConnect VPN server of Cisco Meraki MX and Cisco Meraki Z3 Teleworker Gateway devices could allow an unauthenticated, remote attacker to cause a denial of service (DoS) condition on an affected device. This vulnerability is due to insufficient validation of client-supplied parameters while establishing an SSL VPN session. An attacker could exploit this vulnerability by crafting a malicious request and sending it to the affected device. A successful exploit could allow the attacker to cause the Cisco AnyConnect VPN server to crash and restart, resulting in the failure of the established SSL VPN connections and forcing remote users to initiate a new VPN connection and re-authenticate. A sustained attack could prevent new SSL VPN connections from being established. Note: When the attack traffic stops, the Cisco AnyConnect VPN server recovers gracefully without requiring manual intervention. Cisco Meraki has released software updates that address this vulnerability.

Severity

CVSS 3.1

8.6 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
EPSS
1.1% (unchanged from 1.1% a week ago; 1.1% 30 days ago) estimated probability of exploitation activity in the next 30 days; 68th percentile. Scored 2026-11-21. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2024-11-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-234 Failure to Handle Missing Parameter
OWASP Top 10
A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Analyzed, since modified
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2022-20933 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2022-20933?via=ask-ai-copy and https://cve.bz/cve/CVE-2022-20933?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-20933 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:meraki_mx64_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx64_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx64w_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx64w_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx65_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx65_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx65w_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx65w_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx67_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx67_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx67cw_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx67cw_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx67w_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx67w_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx68_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx68_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx68cw_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx68cw_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx68w_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx68w_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx75_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx75_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx84_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx84_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx85_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx85_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx95_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx95_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx100_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx100_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx105_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx105_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx250_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx250_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx400_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx400_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx450_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx450_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_mx600_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_mx600_firmwarefrom 17.0.0 before 17.10.1
cisco:meraki_vmx_firmwarefrom 16.2.0 before 16.16.6
cisco:meraki_vmx_firmwarefrom 17.0.0 before 17.10.1

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

References

Check your stackJSON