# CVE-2020-3195: Denial of service in Cisco Adaptive Security Appliance (ASA) Software > Remote attackers can cause a memory leak and device reload by sending crafted OSPF packets, leading to denial of service. - **Severity:** High 8.6 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 6 May 2020 - **Updated:** 15 Nov 2024 - **Also known as:** GHSA-868c-7v9p-gmxp ## What is CVE-2020-3195? CVE-2020-3195 is a high-severity denial of service vulnerability in Cisco Adaptive Security Appliance Software, published on 6 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability in the Open Shortest Path First (OSPF) implementation in Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an unauthenticated, remote attacker to cause a memory leak on an affected device. The vulnerability is due to incorrect processing of certain OSPF packets. An attacker could exploit this vulnerability by sending a series of crafted OSPF packets to be processed by an affected device. A successful exploit could allow the attacker to continuously consume memory on an affected device and eventually cause it to reload, resulting in a denial of service (DoS) condition. Weakness: CWE-401 (Missing Release of Memory after Effective Lifetime), CWE-400 (Uncontrolled Resource Consumption) ## Which versions are affected by CVE-2020-3195? It affects 14 products. Products: Cisco Adaptive Security Appliance Software, Cisco Asa 5505 Firmware, Cisco Asa 5510 Firmware, Cisco Asa 5512-X Firmware, Cisco Asa 5515-X Firmware, Cisco Asa 5520 Firmware, Cisco Asa 5525-X Firmware, Cisco Asa 5540 Firmware, Cisco Asa 5545-X Firmware, Cisco Asa 5550 Firmware, Cisco Asa 5555-X Firmware, Cisco Asa 5580 Firmware, Cisco Asa 5585-X Firmware, Cisco Secure Firewall Threat Defense. ## How do I fix CVE-2020-3195? No fix has been published for CVE-2020-3195 yet. Limit exposure of the affected software until one is available. ## Is CVE-2020-3195 being exploited? There is no known exploitation of CVE-2020-3195 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Adaptive Security Appliance Software - [CVE-2025-20333](https://insights.sbomify.com/CVE-2025-20333/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Buffer Overflow (critical 9.9, exploited in the wild) - [CVE-2016-6366](https://insights.sbomify.com/CVE-2016-6366/): Cisco Adaptive Security Appliance (ASA) SNMP Buffer Overflow (high 8.8, exploited in the wild) - [CVE-2026-20349](https://insights.sbomify.com/CVE-2026-20349/): Cisco Secure Firewall Adaptive Security Appliance (ASA) and Secure Firewall Threat Defense (FTD) Heap Inspection (high 8.6, exploited in the wild) - [CVE-2024-20353](https://insights.sbomify.com/CVE-2024-20353/): Cisco ASA and FTD Denial of Service (high 8.6, exploited in the wild) - [CVE-2016-6367](https://insights.sbomify.com/CVE-2016-6367/): Cisco Adaptive Security Appliance (ASA) CLI Remote Code Execution (high 7.8, exploited in the wild) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2020-3195 and fix it if it is affected. What it is: CVE-2020-3195 is a high-severity denial of service vulnerability in Cisco Adaptive Security Appliance Software, published on 6 May 2020. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2020-3195 in the wild and no public exploit code. Affected product: Cisco Adaptive Security Appliance Software. No package-level version data is available, so check the vendor advisory linked from the reference page. Task: 1. 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. 2. 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. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2020-3195/ (Markdown: https://insights.sbomify.com/CVE-2020-3195/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2020-3195 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-3195 - OSV: https://osv.dev/vulnerability/CVE-2020-3195 --- From sbomify Insights: https://insights.sbomify.com/CVE-2020-3195/ Summaries are generated and may contain mistakes; the official description above is the record.