CVE-2025-64344
BaseFortify
Publication date: 2025-11-26
Last updated on: 2025-12-03
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| oisf | suricata | to 7.0.13 (exc) |
| oisf | suricata | From 8.0.0 (inc) to 8.0.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
| CWE-121 | A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability in Suricata occurs when Lua scripts handle large buffers, which can cause a stack overflow. This affects users who use Lua rules and output scripts that process large amounts of data, potentially leading to a crash or denial of service. The issue has been fixed in Suricata versions 7.0.13 and 8.0.2.
How can this vulnerability impact me? :
The vulnerability can lead to a stack overflow causing Suricata to crash or become unavailable, resulting in a denial of service. This impacts the reliability of network intrusion detection and prevention, potentially leaving networks unmonitored or unprotected during the outage.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
Detection can involve monitoring for Suricata Lua scripts processing unusually large buffers, which may indicate attempts to trigger the stack overflow. However, no specific detection commands are provided in the available information.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include upgrading Suricata to version 7.0.13 or 8.0.2 or later, disabling Lua rules and output scripts, or configuring limits such as stream.depth.reassembly and HTTP response body limits (response-body-limit) to less than half the stack size.