CVE-2025-64334: CWE-770: Allocation of Resources Without Limits or Throttling in OISF suricata
CVE-2025-64334 is a high-severity vulnerability in Suricata versions 8. 0. 0 to before 8. 0. 2, where compressed HTTP data can cause unbounded memory growth during decompression due to lack of resource limits. This flaw can lead to denial of service by exhausting system memory. Exploitation requires no authentication or user interaction and can be triggered remotely by sending crafted compressed HTTP responses. The issue is patched in Suricata 8. 0. 2, with workarounds including disabling LZMA decompression or limiting response body size.
AI Analysis
Technical Summary
CVE-2025-64334 is a 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, versions from 8.0.0 up to but not including 8.0.2 contain a flaw in the handling of compressed HTTP data, particularly involving LZMA decompression. When Suricata processes compressed HTTP responses, it does not impose adequate limits on memory allocation during decompression, which can lead to unbounded memory growth. This uncontrolled resource consumption can exhaust system memory, causing Suricata to crash or become unresponsive, effectively resulting in a denial of service (DoS). The vulnerability can be exploited remotely by an unauthenticated attacker who sends specially crafted compressed HTTP traffic to a network monitored by a vulnerable Suricata instance. No user interaction is required, and the attack vector is network-based, making exploitation feasible in many environments. The issue has been addressed in Suricata version 8.0.2 by implementing proper resource limits during decompression. As a temporary mitigation, disabling LZMA decompression or limiting the response-body-limit size in Suricata’s configuration can reduce the risk. There are no known exploits in the wild at the time of publication, but the high CVSS score of 7.5 reflects the significant impact potential. Suricata is widely used in enterprise and critical infrastructure networks for intrusion detection and prevention, making this vulnerability particularly relevant for organizations relying on it for network security monitoring.
Potential Impact
For European organizations, the impact of this vulnerability can be substantial. Suricata is commonly deployed in network security infrastructures to detect and prevent malicious activity. A successful exploitation leading to unbounded memory consumption can cause Suricata instances to crash or become unresponsive, resulting in loss of network visibility and protection. This denial of service can open windows of opportunity for attackers to conduct further attacks undetected. Critical sectors such as finance, energy, telecommunications, and government agencies that rely on Suricata for real-time network monitoring are especially at risk. The disruption of IDS/IPS capabilities can compromise incident response and increase the likelihood of successful intrusions or data breaches. Additionally, the vulnerability’s remote exploitation without authentication lowers the barrier for attackers, increasing the urgency for mitigation. The absence of known exploits in the wild currently reduces immediate risk, but the availability of a patch and clear attack vector means that threat actors could develop exploits rapidly. European organizations with stringent regulatory requirements for cybersecurity and incident detection must prioritize addressing this vulnerability to maintain compliance and operational security.
Mitigation Recommendations
To mitigate CVE-2025-64334 effectively, European organizations should take the following specific steps: 1) Upgrade Suricata to version 8.0.2 or later immediately, as this version includes the official patch that enforces resource limits during decompression. 2) If immediate upgrade is not feasible, configure Suricata to disable LZMA decompression by adjusting the relevant protocol parsers or disabling the feature in the configuration file. 3) Implement strict limits on the response-body-limit parameter to restrict the maximum size of HTTP response bodies processed, thereby preventing excessive memory allocation. 4) Monitor Suricata logs and system resource usage closely for signs of abnormal memory consumption or crashes that could indicate attempted exploitation. 5) Employ network-level protections such as filtering or rate limiting to reduce exposure to malicious compressed HTTP traffic from untrusted sources. 6) Conduct regular vulnerability scanning and penetration testing focused on Suricata deployments to verify the effectiveness of mitigations. 7) Maintain up-to-date threat intelligence feeds and subscribe to OISF security advisories to stay informed of any emerging exploits or related vulnerabilities. These targeted actions go beyond generic advice by focusing on configuration adjustments and monitoring tailored to this specific decompression resource exhaustion issue.
Affected Countries
Germany, France, United Kingdom, Netherlands, Italy, Spain, Sweden, Belgium, Poland, Finland
CVE-2025-64334: CWE-770: Allocation of Resources Without Limits or Throttling in OISF suricata
Description
CVE-2025-64334 is a high-severity vulnerability in Suricata versions 8. 0. 0 to before 8. 0. 2, where compressed HTTP data can cause unbounded memory growth during decompression due to lack of resource limits. This flaw can lead to denial of service by exhausting system memory. Exploitation requires no authentication or user interaction and can be triggered remotely by sending crafted compressed HTTP responses. The issue is patched in Suricata 8. 0. 2, with workarounds including disabling LZMA decompression or limiting response body size.
AI-Powered Analysis
Technical Analysis
CVE-2025-64334 is a 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, versions from 8.0.0 up to but not including 8.0.2 contain a flaw in the handling of compressed HTTP data, particularly involving LZMA decompression. When Suricata processes compressed HTTP responses, it does not impose adequate limits on memory allocation during decompression, which can lead to unbounded memory growth. This uncontrolled resource consumption can exhaust system memory, causing Suricata to crash or become unresponsive, effectively resulting in a denial of service (DoS). The vulnerability can be exploited remotely by an unauthenticated attacker who sends specially crafted compressed HTTP traffic to a network monitored by a vulnerable Suricata instance. No user interaction is required, and the attack vector is network-based, making exploitation feasible in many environments. The issue has been addressed in Suricata version 8.0.2 by implementing proper resource limits during decompression. As a temporary mitigation, disabling LZMA decompression or limiting the response-body-limit size in Suricata’s configuration can reduce the risk. There are no known exploits in the wild at the time of publication, but the high CVSS score of 7.5 reflects the significant impact potential. Suricata is widely used in enterprise and critical infrastructure networks for intrusion detection and prevention, making this vulnerability particularly relevant for organizations relying on it for network security monitoring.
Potential Impact
For European organizations, the impact of this vulnerability can be substantial. Suricata is commonly deployed in network security infrastructures to detect and prevent malicious activity. A successful exploitation leading to unbounded memory consumption can cause Suricata instances to crash or become unresponsive, resulting in loss of network visibility and protection. This denial of service can open windows of opportunity for attackers to conduct further attacks undetected. Critical sectors such as finance, energy, telecommunications, and government agencies that rely on Suricata for real-time network monitoring are especially at risk. The disruption of IDS/IPS capabilities can compromise incident response and increase the likelihood of successful intrusions or data breaches. Additionally, the vulnerability’s remote exploitation without authentication lowers the barrier for attackers, increasing the urgency for mitigation. The absence of known exploits in the wild currently reduces immediate risk, but the availability of a patch and clear attack vector means that threat actors could develop exploits rapidly. European organizations with stringent regulatory requirements for cybersecurity and incident detection must prioritize addressing this vulnerability to maintain compliance and operational security.
Mitigation Recommendations
To mitigate CVE-2025-64334 effectively, European organizations should take the following specific steps: 1) Upgrade Suricata to version 8.0.2 or later immediately, as this version includes the official patch that enforces resource limits during decompression. 2) If immediate upgrade is not feasible, configure Suricata to disable LZMA decompression by adjusting the relevant protocol parsers or disabling the feature in the configuration file. 3) Implement strict limits on the response-body-limit parameter to restrict the maximum size of HTTP response bodies processed, thereby preventing excessive memory allocation. 4) Monitor Suricata logs and system resource usage closely for signs of abnormal memory consumption or crashes that could indicate attempted exploitation. 5) Employ network-level protections such as filtering or rate limiting to reduce exposure to malicious compressed HTTP traffic from untrusted sources. 6) Conduct regular vulnerability scanning and penetration testing focused on Suricata deployments to verify the effectiveness of mitigations. 7) Maintain up-to-date threat intelligence feeds and subscribe to OISF security advisories to stay informed of any emerging exploits or related vulnerabilities. These targeted actions go beyond generic advice by focusing on configuration adjustments and monitoring tailored to this specific decompression resource exhaustion issue.
For access to advanced analysis and higher rate limits, contact root@offseq.com
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: 11/26/2025, 11:10:10 PM
Last updated: 11/27/2025, 12:01:05 AM
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-66040: CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') in spotipy-dev spotipy
LowCVE-2025-64333: CWE-121: Stack-based Buffer Overflow in OISF suricata
HighCVE-2025-64344: CWE-121: Stack-based Buffer Overflow in OISF suricata
HighCVE-2025-64332: CWE-121: Stack-based Buffer Overflow in OISF suricata
HighCVE-2025-64331: CWE-121: Stack-based Buffer Overflow in OISF suricata
HighActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.