Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-64334: CWE-770: Allocation of Resources Without Limits or Throttling in OISF suricata

0
High
VulnerabilityCVE-2025-64334cvecve-2025-64334cwe-770
Published: Wed Nov 26 2025 (11/26/2025, 22:39:15 UTC)
Source: CVE Database V5
Vendor/Project: OISF
Product: suricata

Description

Suricata is a network IDS, IPS and NSM engine developed by the OISF (Open Information Security Foundation) and the Suricata community. In versions from 8.0.0 to before 8.0.2, compressed HTTP data can lead to unbounded memory growth during decompression. This issue has been patched in version 8.0.2. A workaround involves disabling LZMA decompression or limiting response-body-limit size.

AI-Powered Analysis

AILast updated: 12/03/2025, 23:47:09 UTC

Technical Analysis

CVE-2025-64334 is a resource exhaustion vulnerability classified under CWE-770 (Allocation of Resources Without Limits or Throttling) affecting the Suricata network IDS/IPS/NSM engine developed by the Open Information Security Foundation (OISF). Specifically, in Suricata versions from 8.0.0 up to but not including 8.0.2, the handling of compressed HTTP data, particularly involving LZMA decompression, can cause unbounded memory growth. This occurs because the decompression process does not impose limits or throttling on resource allocation, allowing an attacker to send specially crafted compressed HTTP responses that cause Suricata to consume excessive memory. The consequence is a denial of service (DoS) condition where Suricata processes may crash or become unresponsive due to memory exhaustion. The vulnerability is remotely exploitable without authentication or user interaction, as it relies on network traffic that Suricata inspects. The issue was addressed in Suricata version 8.0.2 by implementing appropriate resource limits during decompression. As a workaround before patching, disabling LZMA decompression or limiting the response-body size can mitigate the risk. Although no exploits have been reported in the wild, the high CVSS score of 7.5 reflects the significant impact on availability and ease of exploitation. Suricata is widely used in network security monitoring and intrusion prevention, making this vulnerability relevant for organizations relying on it for network defense.

Potential Impact

For European organizations, this vulnerability poses a significant risk to the availability of network security monitoring and intrusion prevention systems that utilize Suricata versions 8.0.0 to before 8.0.2. Exploitation can lead to denial of service by exhausting memory resources, potentially causing Suricata to crash or become unresponsive. This disruption can blind security teams to ongoing network threats, increasing the risk of undetected attacks. Critical infrastructure sectors such as energy, finance, telecommunications, and government agencies that rely on Suricata for real-time network analysis are particularly vulnerable. The remote and unauthenticated nature of the exploit means attackers can trigger the vulnerability without prior access, increasing the attack surface. Additionally, the inability to inspect network traffic effectively during a DoS event can have cascading effects on incident response and compliance with European cybersecurity regulations like NIS2. The absence of known exploits in the wild reduces immediate risk but does not eliminate the threat, especially as attackers may develop exploits given the public disclosure.

Mitigation Recommendations

European organizations should immediately upgrade Suricata installations to version 8.0.2 or later to apply the official patch addressing this vulnerability. Until patching is feasible, administrators should disable LZMA decompression in Suricata configurations to prevent unbounded memory growth. Additionally, configuring strict limits on the response-body size within Suricata can reduce the risk of resource exhaustion. Network segmentation and filtering can be employed to limit exposure to untrusted HTTP traffic that might carry malicious compressed payloads. Monitoring Suricata process memory usage and setting up alerts for abnormal spikes can provide early warning of exploitation attempts. Organizations should also review and update incident response plans to include scenarios involving Suricata service disruption. Finally, maintaining up-to-date threat intelligence feeds and vendor advisories will help detect emerging exploits targeting this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-10-30T17:40:52.029Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69278547d322a87b22e58f18

Added to database: 11/26/2025, 10:55:03 PM

Last enriched: 12/3/2025, 11:47:09 PM

Last updated: 1/11/2026, 3:30:33 AM

Views: 56

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats