cve.bz

CVE-2024-20509 cisco: Race Condition

5.9 mediumEPSS 0.4%

Medium (5.9) in cisco. EPSS 0.4% 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 Z Series Teleworker Gateway devices could allow an unauthenticated, remote attacker to hijack an AnyConnect VPN session or cause a denial of service (DoS) condition for individual users of the AnyConnect VPN service on an affected device. This vulnerability is due to weak entropy for handlers that are used during the VPN authentication process as well as a race condition that exists in the same process. An attacker could exploit this vulnerability by correctly guessing an authentication handler and then sending crafted HTTPS requests to an affected device. A successful exploit could allow the attacker to take over the AnyConnect VPN session from a target user or prevent the target user from establishing an AnyConnect VPN session with the affected device.

Severity

CVSS 3.1

5.9 medium
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 34th 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: no · Technical impact: partial, assessed 2024-10-02. 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-362 Concurrent Execution using Shared Resource with Improper Synchronization (Race Condition)
OWASP Top 10
A06:2025 Insecure Design
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-2024-20509 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-20509?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-20509?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-2024-20509 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_mx65_firmwarefrom 17.6.0 before 18.211.2
cisco:meraki_mx64_firmwarefrom 17.6.0 before 18.211.2
cisco:meraki_z4c_firmwarefrom 16.2 before 18.211.2
cisco:meraki_z4_firmwarefrom 16.2 before 18.211.2
cisco:meraki_z3c_firmwarefrom 16.2 before 18.211.2
cisco:meraki_z3_firmwarefrom 16.2 before 18.211.2
cisco:meraki_vmx_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx600_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx450_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx400_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx250_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx105_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx100_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx95_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx85_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx84_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx75_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx68w_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx68cw_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx68_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx67w_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx67c_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx67_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx65w_firmwarefrom 16.2 before 18.211.2
cisco:meraki_mx64w_firmwarefrom 16.2 before 18.211.2

Attack patterns (CAPEC)

  • CAPEC-26 Leveraging Race Conditions Likelihood: High · Severity: High
  • CAPEC-29 Leveraging Time-of-Check and Time-of-Use (TOCTOU) Race Conditions Likelihood: High · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON