# CVE-2024-20268: Cisco Adaptive Security Appliance Software and Firepower Threat Defense Software SNMP Denial of Service Vulnerability > An authenticated remote attacker can cause a denial of service on Cisco ASA and FTD devices by sending crafted SNMP packets. - **Severity:** High 7.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:N/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** No - **Published:** 23 Oct 2024 - **Updated:** 24 Oct 2024 - **Also known as:** GHSA-gvjq-f8m6-m457 ## What is CVE-2024-20268? CVE-2024-20268 is a high-severity denial of service vulnerability in Cisco Adaptive Security Appliance Software, published on 23 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description A vulnerability in the Simple Network Management Protocol (SNMP) feature of Cisco Adaptive Security Appliance (ASA) Software and Cisco Firepower Threat Defense (FTD) Software could allow an authenticated, remote attacker to cause an unexpected reload of the device. This vulnerability is due to insufficient input validation of SNMP packets. An attacker could exploit this vulnerability by sending a crafted SNMP request to an affected device using IPv4 or IPv6. A successful exploit could allow the attacker to cause the affected device to reload, resulting in a denial of service (DoS) condition. This vulnerability affects all versions of SNMP (versions 1, 2c, and 3) and requires a valid SNMP community string or valid SNMPv3 user credentials. Weakness: CWE-231 (Improper Handling of Extra Values) ## Which versions are affected by CVE-2024-20268? It affects 2 products. Products: Cisco Adaptive Security Appliance Software, Cisco Secure Firewall Threat Defense. ## How do I fix CVE-2024-20268? No fix has been published for CVE-2024-20268 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-20268 being exploited? There is no known exploitation of CVE-2024-20268 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-2024-20268 and fix it if it is affected. What it is: CVE-2024-20268 is a high-severity denial of service vulnerability in Cisco Adaptive Security Appliance Software, published on 23 Oct 2024. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2024-20268 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-2024-20268/ (Markdown: https://insights.sbomify.com/CVE-2024-20268/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-20268 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-20268 - OSV: https://osv.dev/vulnerability/CVE-2024-20268 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-20268/ Summaries are generated and may contain mistakes; the official description above is the record.