# CVE-2024-20330: Memory corruption in Cisco Firepower Threat Defense Software > Remote attackers can cause memory corruption in the Snort engine, leading to repeated crashes and denial of service for inspected traffic. - **Severity:** High 8.6 (`CVSS:3.1/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:** 23 Oct 2024 - **Updated:** 24 Oct 2024 - **Also known as:** GHSA-prx7-jm7p-362c ## What is CVE-2024-20330? CVE-2024-20330 is a high-severity memory corruption vulnerability in Cisco Secure Firewall Threat Defense, published on 23 Oct 2024. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description A vulnerability in the Snort 2 and Snort 3 TCP and UDP detection engine of Cisco Firepower Threat Defense (FTD) Software for Cisco Firepower 2100 Series Appliances could allow an unauthenticated, remote attacker to cause memory corruption, which could cause the Snort detection engine to restart unexpectedly. This vulnerability is due to improper memory management when the Snort detection engine processes specific TCP or UDP packets. An attacker could exploit this vulnerability by sending crafted TCP or UDP packets through a device that is inspecting traffic using the Snort detection engine. A successful exploit could allow the attacker to restart the Snort detection engine repeatedly, which could cause a denial of service (DoS) condition. The DoS condition impacts only the traffic through the device that is examined by the Snort detection engine. The device can still be managed over the network. Note: Once a memory block is corrupted, it cannot be cleared until the Cisco Firepower 2100 Series Appliance is manually reloaded. This means that the Snort detection engine could crash repeatedly, causing traffic that is processed by the Snort detection engine to be dropped until the device is manually reloaded. Weakness: CWE-788 (Access of Memory Location After End of Buffer) ## Which versions are affected by CVE-2024-20330? It affects 1 product. Products: Cisco Secure Firewall Threat Defense. ## How do I fix CVE-2024-20330? No fix has been published for CVE-2024-20330 yet. Limit exposure of the affected software until one is available. ## Is CVE-2024-20330 being exploited? There is no known exploitation of CVE-2024-20330 in the wild and no public exploit code. ## Other vulnerabilities in Cisco Secure Firewall Threat Defense - [CVE-2024-20412](https://insights.sbomify.com/CVE-2024-20412/): Hardcoded credentials in Cisco Firepower Threat Defense Software (critical 9.3) - [CVE-2024-20339](https://insights.sbomify.com/CVE-2024-20339/): Cisco Firepower Threat Defense Software for Firepower 2100 Series TLS Denial of Service Vulnerability (high 8.6) - [CVE-2024-20351](https://insights.sbomify.com/CVE-2024-20351/): Cisco Firepower Threat Defense Software Snort Firewall Denial of Service Vulnerability (high 8.6) - [CVE-2023-20083](https://insights.sbomify.com/CVE-2023-20083/): Denial of service in Cisco Firepower Threat Defense Software (high 8.6) - [CVE-2023-20244](https://insights.sbomify.com/CVE-2023-20244/): Denial of service in Cisco Firepower Threat Defense Software (high 8.6) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2024-20330 and fix it if it is affected. What it is: CVE-2024-20330 is a high-severity memory corruption vulnerability in Cisco Secure Firewall Threat Defense, published on 23 Oct 2024. 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-2024-20330 in the wild and no public exploit code. Affected product: Cisco Secure Firewall Threat Defense. 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-20330/ (Markdown: https://insights.sbomify.com/CVE-2024-20330/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2024-20330 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-20330 - OSV: https://osv.dev/vulnerability/CVE-2024-20330 --- From sbomify Insights: https://insights.sbomify.com/CVE-2024-20330/ Summaries are generated and may contain mistakes; the official description above is the record.