CVE-2024-20501VulnerabilityPublished 2 Oct 2024Updated 4 Jun 2025

CVE-2024-20501: Cisco Meraki MX Firmware · Out-of-bounds Write

Affects Cisco Meraki MX FirmwareSource CVE Database V5

Not known to be exploited · CVSS 8.6 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score

8.6High

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.5% chance of exploitation in 30 days – higher than 42% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Changed
Confidentiality: None
Integrity: None
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Changed: An exploited vulnerability can affect resources beyond the security scope managed by the security authority of the vulnerable component. In this case, the vulnerable component and the impacted component are different and managed by different security authorities.
Confidentiality: None: There is no loss of confidentiality within the impacted component.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 2 Oct 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

Organizations should immediately verify the firmware versions of their Cisco Meraki MX and Z Series Teleworker Gateway devices and consult Cisco’s security advisories for available patches or firmware updates addressing CVE-2024-20501. Until patches are applied, network administrators should consider implementing the following mitigations: 1) Restrict access to the VPN server management interfaces and SSL VPN endpoints using firewall rules or access control lists (ACLs) to limit exposure to trusted IP ranges. 2) Monitor VPN server logs and network traffic for unusual HTTPS requests or repeated connection resets indicative of exploitation attempts. 3) Employ rate limiting or intrusion prevention systems (IPS) to detect and block malformed or excessive VPN connection attempts. 4) Educate remote users about potential service disruptions and establish contingency plans for critical remote access needs. 5) Coordinate with Cisco support for any recommended configuration changes or temporary workarounds. Proactive vulnerability management and incident response readiness are essential to minimize downtime and operational impact.

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.

Impact

For European organizations, this vulnerability poses a substantial risk to business continuity and secure remote access infrastructure. Many enterprises and public sector entities in Europe rely on Cisco Meraki MX and Z Series devices to provide secure VPN connectivity for remote employees, contractors, and partners. A successful DoS attack could disrupt critical operations by severing VPN connections, delaying workflows, and potentially causing compliance issues if remote access is mandated for regulatory reasons (e.g., GDPR requirements for secure data access). The disruption could be particularly impactful for sectors with high remote workforce dependency such as finance, healthcare, government, and technology. Additionally, the ability to cause repeated VPN service outages without authentication lowers the barrier for attackers, increasing the likelihood of opportunistic or targeted attacks. While confidentiality and integrity are not directly compromised, the availability impact can indirectly affect security posture by forcing fallback to less secure access methods or causing operational delays.

References

sec.cloudapps.cisco.com/security/center/content/CiscoSecurityAdvisory/cisco-sa-meraki-mx-vpn-dos-QTRHzG2 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 6 Jul 2025, 21:28 UTC

Technical details

References

Community reviews

Related threats