CVE-2025-64331
BaseFortify
Publication date: 2025-11-26
Last updated on: 2025-12-08
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-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). |
| CWE-787 | The product writes data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a stack overflow in Suricata, a network IDS, IPS, and NSM engine. It occurs during large HTTP file transfers if the user has increased the HTTP response body limit and enabled logging of printable HTTP bodies. This can cause the software to overflow its stack, potentially leading to crashes or other unintended behavior. The issue has been fixed in versions 7.0.13 and 8.0.2.
How can this vulnerability impact me? :
The vulnerability can cause Suricata to experience a stack overflow during large HTTP file transfers under certain configurations, which may lead to denial of service by crashing the application or disrupting network monitoring and intrusion detection capabilities. This can reduce the effectiveness of network security monitoring and potentially allow malicious traffic to go undetected.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately upgrade Suricata to version 7.0.13 or 8.0.2 or later. Alternatively, as a workaround, revert to the default HTTP response body limits and/or disable the logging of printable HTTP bodies, since body logging is disabled by default.