cve.bz

CVE-2024-20498 cisco: Double Free

7.5 highEPSS 0.5%

High (7.5) in cisco. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
EPSS
0.5% (unchanged from 0.5% a week ago; 0.5% 30 days ago) estimated probability of exploitation activity in the next 30 days; 44th 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: yes · 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-415 Double Free
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-20498 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2024-20498?via=ask-ai-copy and https://cve.bz/cve/CVE-2024-20498?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-20498 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

References

Check your stackJSON