{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-20212 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-20212 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-20212 is a high-severity denial of service vulnerability in Cisco Meraki MX Firmware, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-20212 and fix it if it is affected.\n\nWhat it is: CVE-2025-20212 is a high-severity denial of service vulnerability in Cisco Meraki MX Firmware, published on 2 Apr 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-20212 in the wild and no public exploit code.\n\nAffected product: Cisco Meraki MX Firmware. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-20212/ (Markdown: https://insights.sbomify.com/CVE-2025-20212/index.md)","id":"CVE-2025-20212","markdown":"https://insights.sbomify.com/CVE-2025-20212/index.md","name":"CVE-2025-20212","record":{"aliases":["GHSA-mf93-68c7-8cg2"],"analysis":{"component_type":"network_device","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"yes","non_default_config":false,"product_category":"Cisco Meraki MX","requires_auth":"low_privilege","summary":"An authenticated remote attacker can cause a denial of service in the Cisco AnyConnect VPN server by supplying crafted attributes during SSL session establishment.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"cisco","cpe":[],"cvss":{"score":7.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H","version":"3.1"},"cwes":[{"id":"CWE-457","name":"Use of Uninitialized Variable"}],"description":"A vulnerability in the Cisco AnyConnect VPN server of Cisco Meraki MX and Cisco Meraki Z Series devices could allow an authenticated, remote attacker to cause a denial of service (DoS) condition in the Cisco AnyConnect service on an affected device. To exploit this vulnerability, the attacker must have valid VPN user credentials on the affected device.\r\n\r This vulnerability exists because a variable is not initialized when an SSL VPN session is established. An attacker could exploit this vulnerability by supplying crafted attributes while establishing an SSL VPN session with 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 sessions and forcing remote users to initiate a new VPN connection and reauthenticate. A sustained attack could prevent new SSL VPN connections from being established.\r\n\r Note: When the attack traffic stops, the Cisco AnyConnect VPN server recovers without manual intervention.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Denial of service in Cisco Meraki MX Firmware","id":"CVE-2025-20212","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Cisco Catalyst SDWAN Manager Arbitrary File Overwrite Vulnerability","id":"CVE-2025-20213"},"packages":[],"prev":{"headline":"Cisco BroadWorks Application Delivery Platform Software Cross-Site Scripting Vulnerability","id":"CVE-2025-20211"},"products":["Cisco Meraki MX Firmware"],"published":"2025-04-02","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-04-02","vendors":["Cisco"]},"summary":"An authenticated remote attacker can cause a denial of service in the Cisco AnyConnect VPN server by supplying crafted attributes during SSL session establishment.","url":"https://insights.sbomify.com/CVE-2025-20212/"}