Skip to content
Fencer Intel
high 8.6

CVE-2022-20933 json

Cisco Meraki MX and Z3 Teleworker Gateway VPN Denial of Service Vulnerability

published 4y ago modified 4mo ago also EUVD-2022-26183

cvss
8.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
1.1%
EPSS 1.1% chance of exploitation in 30 days, percentile 66%
public exploits
0
none known

Summary

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.

Patch / fix

  • cisco meraki_mx64_firmware 16.16.6, 17.10.1
  • cisco meraki_mx64w_firmware 16.16.6, 17.10.1
  • cisco meraki_mx65_firmware 16.16.6, 17.10.1
  • cisco meraki_mx65w_firmware 16.16.6, 17.10.1
  • cisco meraki_mx67_firmware 16.16.6, 17.10.1
  • cisco meraki_mx67cw_firmware 16.16.6, 17.10.1
  • cisco meraki_mx67w_firmware 16.16.6, 17.10.1
  • cisco meraki_mx68_firmware 16.16.6, 17.10.1
  • cisco meraki_mx68cw_firmware 16.16.6, 17.10.1
  • cisco meraki_mx68w_firmware 16.16.6, 17.10.1
  • cisco meraki_mx75_firmware 16.16.6, 17.10.1
  • cisco meraki_mx84_firmware 16.16.6, 17.10.1
  • cisco meraki_mx85_firmware 16.16.6, 17.10.1
  • cisco meraki_mx95_firmware 16.16.6, 17.10.1
  • cisco meraki_mx100_firmware 16.16.6, 17.10.1
  • cisco meraki_mx105_firmware 16.16.6, 17.10.1
  • cisco meraki_mx250_firmware 16.16.6, 17.10.1
  • cisco meraki_mx400_firmware 16.16.6, 17.10.1
  • cisco meraki_mx450_firmware 16.16.6, 17.10.1
  • cisco meraki_mx600_firmware 16.16.6, 17.10.1

Is CVE-2022-20933 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
2y ago

Exploit prediction

1.14% chance of exploitation in the next 30 days, higher than 66% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
NVD 3.1 8.6 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Affected products

  • Cisco Cisco Meraki MX Firmware

Classification

Weakness
  • CWE-234 Failure to Handle Missing Parameter

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.