You are viewing this page in an unauthorized frame window.
This is a potential security issue, you are being redirected to
https://nvd.nist.gov
An official website of the United States government
Official websites use .gov
A .gov website belongs to an official government organization in the United States.
Secure .gov websites use HTTPS
A lock () or https:// means you've safely connected to the .gov website. Share sensitive information only on official, secure websites.
This CVE record has been updated after NVD enrichment efforts were completed. Enrichment data supplied by the NVD may require amendment due to these changes.
Current Description
Multiple vulnerabilities in the Cisco AnyConnect VPN server of Cisco Meraki MX and Cisco Meraki Z Series Teleworker Gateway devices could allow an unauthenticated, remote attacker to cause a DoS condition in the AnyConnect service on an affected device.
These vulnerabilities are due to insufficient validation of client-supplied parameters while establishing an SSL VPN session. An attacker could exploit these vulnerabilities by sending a crafted HTTPS request to the VPN server of an affected device. A successful exploit could allow the attacker to cause the Cisco AnyConnect VPN server to restart, resulting in the failure of the established SSL VPN connections and forcing remote users to initiate a new VPN connection and reauthenticate. 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.
Multiple vulnerabilities in the Cisco AnyConnect VPN server of Cisco Meraki MX and Cisco Meraki Z Series Teleworker Gateway devices could allow an unauthenticated, remote attacker to cause a DoS condition in the AnyConnect service on an affected device.
These vulnerabilities are due to insufficient validation of client-supplied parameters while establishing an SSL VPN session. An attacker could exploit these vulnerabilities by sending a crafted HTTPS request to the VPN server of an affected device. A successful exploit could allow the attacker to cause the Cisco AnyConnect VPN server to restart, resulting in the failure of the established SSL VPN connections and forcing remote users to initiate a new VPN connection and reauthenticate. 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.
Metrics
NVD enrichment efforts reference publicly available information to associate
vector strings. CVSS information contributed by other sources is also
displayed.
By selecting these links, you will be leaving NIST webspace.
We have provided these links to other web sites because they
may have information that would be of interest to you. No
inferences should be drawn on account of other sites being
referenced, or not, from this page. There may be other web
sites that are more appropriate for your purpose. NIST does
not necessarily endorse the views expressed, or concur with
the facts presented on these sites. Further, NIST does not
endorse any commercial products that may be mentioned on
these sites. Please address comments about this page to [email protected].
CVE Modified by Cisco Systems, Inc.6/04/2025 5:15:36 PM
Action
Type
Old Value
New Value
Changed
Description
Multiple vulnerabilities in the Cisco AnyConnect VPN server of Cisco Meraki MX and Cisco Meraki Z Series Teleworker Gateway devices could allow an unauthenticated, remote attacker to cause a DoS condition in the AnyConnect service on an affected device.
These vulnerabilities are due to insufficient validation of client-supplied parameters while establishing an SSL VPN session. An attacker could exploit these vulnerabilities by sending a crafted HTTPS request to the VPN server of an affected device. A successful exploit could allow the attacker to cause the Cisco AnyConnect VPN server to restart, resulting in the failure of the established SSL VPN connections and forcing remote users to initiate a new VPN connection and reauthenticate. 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.
Multiple vulnerabilities in the Cisco AnyConnect VPN server of Cisco Meraki MX and Cisco Meraki Z Series Teleworker Gateway devices could allow an unauthenticated, remote attacker to cause a DoS condition in the AnyConnect service on an affected device.
These vulnerabilities are due to insufficient validation of client-supplied parameters while establishing an SSL VPN session. An attacker could exploit these vulnerabilities by sending a crafted HTTPS request to the VPN server of an affected device. A successful exploit could allow the attacker to cause the Cisco AnyConnect VPN server to restart, resulting in the failure of the established SSL VPN connections and forcing remote users to initiate a new VPN connection and reauthenticate. 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.
Initial Analysis by NIST10/08/2024 2:32:54 PM
Action
Type
Old Value
New Value
Added
CVSS V3.1
NIST AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Added
CWE
NIST CWE-415
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx100_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx100:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx105_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx105:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx250_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx250:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx400_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx400:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx450_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx450:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx600_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx600:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx64_firmware:*:*:*:*:*:*:*:* versions from (including) 17.6.0 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx64:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx64w_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx64w:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx65_firmware:*:*:*:*:*:*:*:* versions from (including) 17.6.0 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx65:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx65w_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx65w:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx67_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx67:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx67c_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx67c:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx67w_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx67w:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx68_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx68:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx68cw_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx68cw:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx68w_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx68w:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx75_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx75:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx84_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx84:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx85_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx85:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_mx95_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_mx95:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_vmx_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_vmx:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_z3_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_z3:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_z3c_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_z3c:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_z4_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_z4:-:*:*:*:*:*:*:*
Added
CPE Configuration
AND
OR
*cpe:2.3:o:cisco:meraki_z4c_firmware:*:*:*:*:*:*:*:* versions from (including) 16.2 up to (excluding) 18.211.2
OR
cpe:2.3:h:cisco:meraki_z4c:-:*:*:*:*:*:*:*
Changed
Reference Type
https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-meraki-mx-vpn-dos-QTRHzG2 No Types Assigned
New CVE Received from Cisco Systems, Inc.10/02/2024 3:15:13 PM
Action
Type
Old Value
New Value
Added
Description
Multiple vulnerabilities in the Cisco AnyConnect VPN server of Cisco Meraki MX and Cisco Meraki Z Series Teleworker Gateway devices could allow an unauthenticated, remote attacker to cause a DoS condition in the AnyConnect service on an affected device.
These vulnerabilities are due to insufficient validation of client-supplied parameters while establishing an SSL VPN session. An attacker could exploit these vulnerabilities by sending a crafted HTTPS request to the VPN server of an affected device. A successful exploit could allow the attacker to cause the Cisco AnyConnect VPN server to restart, resulting in the failure of the established SSL VPN connections and forcing remote users to initiate a new VPN connection and reauthenticate. 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.
Added
CVSS V3.1
Cisco Systems, Inc. AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H
Added
CWE
Cisco Systems, Inc. CWE-415
Added
Reference
Cisco Systems, Inc. https://sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-meraki-mx-vpn-dos-QTRHzG2 [No types assigned]
Quick Info
CVE Dictionary Entry: CVE-2024-20498 NVD
Published Date: 10/02/2024 NVD
Last Modified: 06/17/2026
Source: Cisco Systems, Inc.