CVE-2024-20513

MEDIUM
5.3
CVSS Score
Published: October 2, 2024 at 06:23 PM UTC
Updated: June 17, 2026 at 07:07 AM UTC
51 products affected across 1 vendorMeraki MX68W FirmwareMeraki MX68CW FirmwareMeraki MX64W Firmware

Using Cisco Meraki MX Firmware by Cisco?

Get instant alerts when new vulnerabilities affect Cisco Meraki MX Firmware - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
MEDIUM5.3
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

A vulnerability 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 for targeted users of the AnyConnect service on an affected device. This vulnerability is due to insufficient entropy for handlers that are used during SSL VPN session establishment. An unauthenticated attacker could exploit this vulnerability by brute forcing valid session handlers. An authenticated attacker could exploit this vulnerability by connecting to the AnyConnect VPN service of an affected device to retrieve a valid session handler and, based on that handler, predict further valid session handlers. The attacker would then send a crafted HTTPS request using the brute-forced or predicted session handler to the AnyConnect VPN server of the device. A successful exploit could allow the attacker to terminate targeted SSL VPN sessions, forcing remote users to initiate new VPN connections and reauthenticate.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

16.2 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx100 (same device)
16.2 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx105 (same device)
16.2 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx250 (same device)
16.2 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx400 (same device)
16.2 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx450 (same device)
16.2 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx600 (same device)
17.6.0 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx64 (same device)
16.2 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx64w (same device)
17.6.0 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx65 (same device)
16.2 ≤ v < 18.211.2
Affected range stops below 18.211.2, so it looks safe — our inference, not a vendor statement
cisco-meraki-mx65w (same device)

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
NONE
Integrity
NONE
Availability
LOW
Vector?

Quick Info

StatusMODIFIED
CWE
CWE-639

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card